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 weekly release process does not need to run any week that there are no new commits. The workflow should detect if there are any commits that have been added to the branch it is running on since the previous release. If there are no new commits it should exit early.
I think the best way for the process to determine if there are any new commits is for it to try to see if there are any release tags on the current commit. If there are not, then the commit must be new. If there are then the commit already has a release tag and probably does not need another release.
Another option may be to look at the releases page, however this option wont work until after we actually cut releases from this process to the releases page.
Other options may also exist.
The text was updated successfully, but these errors were encountered:
The weekly release process does not need to run any week that there are no new commits. The workflow should detect if there are any commits that have been added to the branch it is running on since the previous release. If there are no new commits it should exit early.
I think the best way for the process to determine if there are any new commits is for it to try to see if there are any release tags on the current commit. If there are not, then the commit must be new. If there are then the commit already has a release tag and probably does not need another release.
Another option may be to look at the releases page, however this option wont work until after we actually cut releases from this process to the releases page.
Other options may also exist.
The text was updated successfully, but these errors were encountered: