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
Just if easily possible: ATM issues are closed whenever PRs fix them in master, but not necessarily released&deployed to openneuro instance. For a reporter/user it is hard(er) to track when to check on whether issue was fixed for him/her.
in case of dandi we use intuit's auto with released plugin (config file). With that, each issue and PR get annotation whenever they get "released", which makes it really convenient later to see which version of client is minimal necessary for a specific issue to be addressed or either PR in the archive backend was released/deployed already. See e.g. dandi/dandi-archive#2122 (comment) for an example of such annotation.
So I wondered what is your release process and either it would be easily to add a similar feature
Alternatives
No response
Do you have any interest in helping implement the feature?
Yes, but I would need guidance
Additional information / screenshots
No response
The text was updated successfully, but these errors were encountered:
given that the latest tag is 4.29.9 while latest "release" is 4.29.5, I guess there is no automation at least to craft releases? (I only see workflows which react to pushed tags).
FWIW, in general I would recommend that auto but keep in mind its still present annoying bug intuit/auto#1294 if you are managing CHANGELOG with it -- the "workaround" is simply to "release often", then changes to changelog are short and bug is avoided ;)
What would you like to see added?
Just if easily possible: ATM issues are closed whenever PRs fix them in master, but not necessarily released&deployed to openneuro instance. For a reporter/user it is hard(er) to track when to check on whether issue was fixed for him/her.
in case of dandi we use intuit's auto with released plugin (config file). With that, each issue and PR get annotation whenever they get "released", which makes it really convenient later to see which version of client is minimal necessary for a specific issue to be addressed or either PR in the archive backend was released/deployed already. See e.g. dandi/dandi-archive#2122 (comment) for an example of such annotation.
So I wondered what is your release process and either it would be easily to add a similar feature
Alternatives
No response
Do you have any interest in helping implement the feature?
Yes, but I would need guidance
Additional information / screenshots
No response
The text was updated successfully, but these errors were encountered: