-
Notifications
You must be signed in to change notification settings - Fork 125
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update logic for Increment Version Number (#1108)
**Problem** If you define the repoVersion in .github/AL-Go-Settings.json it isn't updated when running the Increment Version Number workflow. In our case, the would like to keep the repoVersion the same across all Al-Go projects so having repoVersion defined on repo level makes sense for us (even if it is a project setting) **Proposed Solution** * If repoVersion exists on project level (recommended), we only update it there. * If repoVersion doesn't exist in project level but exists on repo level, we update it on repo level (what we want in our case) * if repoVersion is neither defined on project level or repo level, force create it on project level Fixes #1105 --------- Co-authored-by: Freddy Kristiansen <[email protected]>
- Loading branch information
1 parent
6f8c7f3
commit c9e9cc3
Showing
3 changed files
with
62 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters