-
Notifications
You must be signed in to change notification settings - Fork 362
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
Have one workflow ignore the state saved by another #1137
Labels
feature request
New feature or request to improve the current logic
Comments
rcomer
added
feature request
New feature or request to improve the current logic
needs triage
labels
Feb 22, 2024
Hello @rcomer |
Old issue but PR is created for this issue. |
Thank you @echang49! |
It will be really great if #1169 is merged. As mentioned in the PR I am hitting the same issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
Given two workflows in the same repo using this action, have one workflow ignore the state saved by another. I think either of these two options would work for us:
Justification:
Over in Matplotlib, we are using the action to slowly work through a large backlog of issues. We want to keep notifications fairly minimal so have
operations-per-run
set low. However, we don't want steps like removing the label after update or closing the issue to wait until we've worked through the whole backlog. So when we updated to v9, we also added a second workflow using the action withdays-before-stale=-1
and a much higheroperations-per-run
(see my PR here matplotlib/matplotlib#27523). The two workflows run on alternate days. Once #1136 is fixed, I believe what will happen isSince only the original workflow is adding the label, we still do not make progress through our backlog! If each workflow has its own state, this would not be a problem. Also if we could tell the second workflow not to look for a state, it would not be a problem.
Are you willing to submit a PR?
Willing, yes, but I do not have skills with typescript....
The text was updated successfully, but these errors were encountered: