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

Prevent running the same workflows twice on the same commit #34

Closed
reece opened this issue Sep 26, 2023 · 5 comments
Closed

Prevent running the same workflows twice on the same commit #34

reece opened this issue Sep 26, 2023 · 5 comments
Labels
closed-by-stale stale Issue is stale and subject to automatic closing

Comments

@reece
Copy link
Member

reece commented Sep 26, 2023

Is your feature request related to a problem? Please describe.

We currently run the same workflow twice for each commit in a PR. For example, in #32:

image

Describe the solution you'd like

A workflow should be run exactly once for each environment configuration. [This issue has been encountered by many others] (https://github.com/orgs/community/discussions/26276).

We should consider these cases:

  • commit to main (always/usually a merge) by codeowner
  • commit to branch other than main with or without PR by anyone with permissions to do so
  • PR from remote (i.e., not biocommons org) repo
@github-actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the stale Issue is stale and subject to automatic closing label Oct 27, 2023
Copy link

github-actions bot commented Nov 3, 2023

This issue was closed because it has been stalled for 7 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 3, 2023
@reece reece reopened this Feb 19, 2024
@reece reece removed the stale Issue is stale and subject to automatic closing label Feb 19, 2024
@reece
Copy link
Member Author

reece commented Feb 19, 2024

This issue was closed by stalebot. It has been reopened to give more time for community review. See biocommons coding guidelines for stale issue and pull request policies. This resurrection is expected to be a one-time event.

Copy link

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the stale Issue is stale and subject to automatic closing label May 20, 2024
Copy link

This issue was closed because it has been stalled for 7 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-by-stale stale Issue is stale and subject to automatic closing
Projects
None yet
Development

No branches or pull requests

1 participant