You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: