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

Github Actions spawns too many workflows during development #278

Closed
laceysanderson opened this issue Oct 3, 2022 · 0 comments
Closed

Github Actions spawns too many workflows during development #278

laceysanderson opened this issue Oct 3, 2022 · 0 comments

Comments

@laceysanderson
Copy link
Member

The current schema for one job per workflow was done to get around badge limitations in providing the compatibility table on the README. However, during development this spawns a large number of rows in the actions table making it hard to find specific branch results.

My proposed solution is to keep the current workflows but have them only triggered on our master branch. Then to have a single workflow with multiple jobs that is triggered for branch push and PRs.

This way during development one push only spawns on record in the action table and you have a nice summary page for all versions. Additionally, we will still support our grid on the main branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant