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
We should use versions (tags) and create releases of the workflows to ease the use and update of re-usable workflows.
Although using the commit SHA is the most secure and stable way according to the docs, it means it is less easy to know if the workflow uses the latest version.
So instead of graasp/graasp-deploy/.github/workflows/cintegration-s3-apps.yml@a5e6f97c18c86d97e3e8f15b27e4d898746327cf we could use graasp/graasp-deploy/.github/workflows/cintegration-s3-apps.yml@v1
The text was updated successfully, but these errors were encountered:
We should use versions (tags) and create releases of the workflows to ease the use and update of re-usable workflows.
Although using the commit SHA is the most secure and stable way according to the docs, it means it is less easy to know if the workflow uses the latest version.
So instead of
graasp/graasp-deploy/.github/workflows/cintegration-s3-apps.yml@a5e6f97c18c86d97e3e8f15b27e4d898746327cf
we could usegraasp/graasp-deploy/.github/workflows/cintegration-s3-apps.yml@v1
The text was updated successfully, but these errors were encountered: