Skip to content
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

Workflow: run CI only native-image upon release #4697

Merged
merged 1 commit into from
Dec 30, 2024

Conversation

kitbellew
Copy link
Collaborator

Also, do not run CI when tagging; when the final commit of a release is merged, currently CI is invoked 3 times:

  • upon commit merge into main (triggered by push to branch main)
  • upon release (triggered by release published)
  • upon tagging along with release (triggered by push to tag vX.Y.Z)

Let's remove the last trigger and run only native-image (which uploads release artifacts) on release trigger, as all the rest of the checks would have been run on the same commit when it had been originally pushed to main.

Also, do not run CI when tagging; when the final commit of a release is
merged, currently CI is invoked 3 times:
- upon commit merge into main (triggered by push to branch main)
- upon release (triggered by release published)
- upon tagging along with release (triggered by push to tag `vX.Y.Z`)

Let's remove the last trigger and run only native-image (which uploads
release artifacts) on release trigger, as all the rest of the checks
would have been run on the same commit when it had been originally
pushed to main.
@@ -3,7 +3,7 @@ on:
push:
branches:
- main
tags:
tags_ignore:
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

perhaps this part should be completely removed, not sure

Copy link
Contributor

Choose a reason for hiding this comment

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

Alternatively, we could remove the release below, no? Since when creating a release a tag is pushed anyway

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

i think release published is needed since that's where it puts the assets. scalameta triggers just on tagging but it doesn't have assets.

Copy link
Contributor

@tgodzik tgodzik left a comment

Choose a reason for hiding this comment

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

I think we can just remove one of those sections, but it's fine either way

@kitbellew kitbellew merged commit 723bc9f into scalameta:main Dec 30, 2024
21 checks passed
@kitbellew kitbellew deleted the 4697 branch December 30, 2024 15:01
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