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
Some thoughts: 💡 (I will move this to discussion tab soon as this is not really an issue or need a workitem)
I think we should stick to current release practise rather then hookign with every merge to main branch of we can scope if a release is created than only trigger.
Some sample steps we could do:
The image for this repo is published in MCR one way we can do this is to add a creds via GitHub env var for publishing reasons.
But then we should really re-visit the admin access for this project.
Any further thoughts, please feel free to add otherwise I will move this to discussion.
The text was updated successfully, but these errors were encountered:
Some thoughts: 💡 (I will move this to discussion tab soon as this is not really an issue or need a workitem)
I think we should stick to current release practise rather then hookign with every merge to main branch of we can scope if a release is created than only trigger.
Some sample steps we could do:
MCR
one way we can do this is to add a creds via GitHubenv var
for publishing reasons.admin
access for this project.Any further thoughts, please feel free to add otherwise I will move this to discussion.
The text was updated successfully, but these errors were encountered: