up-to-date action can be activated by auto-merge-bot #272
Conversation
This file contains 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
muharem
approved these changes
Apr 11, 2024
Bullrich
force-pushed
the
auto-merge/enable-up-to-date
branch
from
5e2a00c to
5283d4c
Compare
bkchr
approved these changes
Apr 20, 2024
Bullrich
force-pushed
the
auto-merge/enable-up-to-date
branch
from
5283d4c to
496df37
Compare
|
/merge |
1 similar comment
|
/merge |
|
Enabled Available commands
For more information see the documentation |
Linked actions so that, when auto-merge is enabled, it will trigger up-to-date to update every PR (including this one) Resolves paritytech/up-to-date-action#14
This latest change include paritytech/up-to-date-action#17 which stops the action from updating PRs which are already up to date
Let's use github's tools when possible as they _should_ be more secure
auto-merge was automatically disabled
April 24, 2024 12:48
Head branch was pushed to by a user without write access
Bullrich
force-pushed
the
auto-merge/enable-up-to-date
branch
from
496df37 to
3dd6c96
Compare
|
/merge |
|
Enabled Available commands
For more information see the documentation |
Failed to update PR ❌There was an error while trying to keep this PR You may have conflicts More info in the logs 📋 |
ordian
approved these changes
May 7, 2024
fellowship-merge-bot
bot
merged commit 2663a3a
into
polkadot-fellows:main
37 checks passed
This was referenced May 7, 2024
Bullrich
added a commit
to Bullrich/polkadot-fellows-runtimes
that referenced
this pull request
May 21, 2024
As explained in paritytech/up-to-date-action#18, the issue is caused because the `skipped` event is treated as `completed`. Until a better solution is generated, let's remove this event and triggered it only in pushes. This reverts polkadot-fellows#272
1 task
fellowship-merge-bot bot
pushed a commit
that referenced
this pull request
May 22, 2024
As explained in paritytech/up-to-date-action#18 (comment), the issue is caused because the `skipped` event is treated as `completed`. Until a better solution is generated, let's remove this event and trigger it only in pushes. This reverts #272 - [x] Does not require a CHANGELOG entry
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
triggered up-to-date when auto-merge is enabled
Updated
up-to-dateaction's versionreplaced github action for github's own action
Does not require a CHANGELOG entry