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
Containerd projects today use the latest release of project-checks in their workflow. Changes merged to projects-checks are not immediately available to all the dependent repositories.
A good mechanism would be to auto release a new version of project-checks based on certain conditions( maybe commit message).
This way the only change required would be to point dependent repositories to the latest version of project-checks.
Containerd projects today use the latest release of project-checks in their workflow. Changes merged to projects-checks are not immediately available to all the dependent repositories.
A good mechanism would be to auto release a new version of project-checks based on certain conditions( maybe commit message).
This way the only change required would be to point dependent repositories to the latest version of project-checks.
We could use a github action for auto releasing repositories.
The text was updated successfully, but these errors were encountered: