fix: Skip package if the last commit is after the comment - #3184
Merged
Keith-CY merged 1 commit intoJun 18, 2024
Conversation
Keith-CY
reviewed
Jun 13, 2024
yanguoyu
force-pushed
the
feat-package-last-commit
branch
from
June 13, 2024 02:35
82c97d1 to
ce6aff4
Compare
Keith-CY
approved these changes
Jun 13, 2024
devchenyan
approved these changes
Jun 16, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I am checking no commit after the trigger comment. If someone pushes a new commit, the package should be repacked again to include the latest commit.
https://github.com/yanguoyu/neuron/actions/runs/9484668688 is the failed example.
https://github.com/yanguoyu/neuron/actions/runs/9484691876 is the success example.