search

microsoft / AL-Go

The plug-and-play DevOps solution for Business Central app development on GitHub
MIT License
280 stars 115 forks source link

Increment Version Number - repoVersion in .github/AL-Go-Settings.json is not updated #1105

Closed aholstrup1 closed 3 months ago

aholstrup1 commented 3 months ago

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)

freddydk commented 3 months ago

Implementation wise, we should probably update the repoVersion in repo settings AND project settings (if it exists) and we should create repoVersion in project settings if it doesn't exist in repo settings. We should never create it in repo settings and we shouldn't create it in project settings if it exists in repo settings.

Make sense?

aholstrup1 commented 3 months ago

I agree. Seems like a good approach :)