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

bot PR workflow should not overwrite existing project status #63

Open
surchs opened this issue Oct 24, 2023 · 2 comments
Open

bot PR workflow should not overwrite existing project status #63

surchs opened this issue Oct 24, 2023 · 2 comments
Labels
usability Issue affecting user or developer experience.

Comments

@surchs
Copy link
Contributor

surchs commented Oct 24, 2023

Our bot PR mover workflow https://github.com/neurobagel/planning/blob/3c1a6e2f6ddc6724dbf8558946f4bc00157ab4ff/.github/workflows/global_move_bot_pr_to_board.yml runs twice a day and then

  • finds all open PRs with the _bot label and
  • moves them into the Community column on the board

This is great unless

  • the PR is already on the board
  • we have manually given the PR a meaningful status other than Community and want to keep it

The simplest solution would be to check if the PR already has a Status value set, and if so, leave it alone.

@surchs surchs added usability Issue affecting user or developer experience. type:bug labels Oct 24, 2023
Copy link

github-actions bot commented Jan 8, 2024

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

  • prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
  • close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
  • archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
    apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
    label in the future. Use sparingly!

@github-actions github-actions bot added the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Jan 8, 2024
@alyssadai alyssadai transferred this issue from neurobagel/planning Mar 20, 2024
@github-actions github-actions bot removed the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Mar 21, 2024
Copy link

github-actions bot commented Jun 5, 2024

We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:

  • prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
  • close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
  • archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
    apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
    label in the future. Use sparingly!

@github-actions github-actions bot added the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Jun 5, 2024
@surchs surchs removed the type:bug label Dec 17, 2024
@github-actions github-actions bot removed the _flag:stale [BOT ONLY] Flag issue that hasn't been updated in a while and needs to be triaged again label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
usability Issue affecting user or developer experience.
Projects
Status: No status
Development

No branches or pull requests

1 participant