Skip to content

chore: setup ci #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 7 commits into
base: main
Choose a base branch
from
Draft

chore: setup ci #2

wants to merge 7 commits into from

Conversation

3arthqu4ke
Copy link
Member

@3arthqu4ke 3arthqu4ke commented Dec 7, 2024

  • This PR must be REBASE merged

@3arthqu4ke 3arthqu4ke force-pushed the setup-ci branch 3 times, most recently from 7c57752 to cf77a87 Compare December 7, 2024 10:46
@3arthqu4ke 3arthqu4ke marked this pull request as draft December 7, 2024 11:02
@3arthqu4ke 3arthqu4ke force-pushed the setup-ci branch 7 times, most recently from 2b388a3 to 38cb24e Compare December 7, 2024 11:47
@3arthqu4ke 3arthqu4ke marked this pull request as ready for review December 7, 2024 11:55
@3arthqu4ke 3arthqu4ke requested a review from ChipWolf December 7, 2024 11:55
uses: useblacksmith/cache@v5
with:
path: build
key: build-${{ inputs.mc }}-${{ hashFiles('./*') }}
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not great and should exclude files like release-please-config.json, README.MD and LICENSE, but besides those all other files affect ci, code or build system and changes should satisfy a rebuild of everything

if "${{ steps.filter.outcome }}" == "success":
# TODO: if only README or LICENSE changed, no need to run all versions!
# dirs_to_filter = json.loads('${{ steps.filter.outputs.changes }}')
versions_to_run = ['all']
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See above, almost all files are ci, code or build system now and should cause everything to be rebuild

@3arthqu4ke
Copy link
Member Author

3arthqu4ke commented Dec 7, 2024

It would probably make it simpler to place all code in a subdirectory again?
That way we simply need to check for changes in that directory, .github and api.

@ChipWolf
Copy link
Member

ChipWolf commented Dec 9, 2024

It would probably make it simpler to place all code in a subdirectory again? That way we simply need to check for changes in that directory, .github and api.

I would encourage this yes.

Copy link
Member

@ChipWolf ChipWolf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move gradle project to subdirectory

@ChipWolf ChipWolf changed the title feat(ci): setup ci chore: setup ci Dec 10, 2024
@ChipWolf ChipWolf marked this pull request as draft December 11, 2024 23:07
@ChipWolf ChipWolf force-pushed the setup-ci branch 4 times, most recently from a986ca4 to 4f53f57 Compare December 12, 2024 01:29
@ChipWolf ChipWolf force-pushed the setup-ci branch 7 times, most recently from a220151 to 58fb829 Compare December 15, 2024 00:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants