Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update README.md #73

Merged
merged 1 commit into from
Aug 23, 2024
Merged

Update README.md #73

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ There are 2 automated work flows triggering repository actions:
* reruns all of the check-consistency code
* adds the new turtle(ttl) content to master as a github action commit
* publishes new and changed content to the registry
* this uses action secrets, ensure the full URI username and a token are entered in the action secrets in settings
* this uses action secrets, ensure the full URI username and a token are entered in the action secrets in settings
* note, if the push to master fails then it's best not to just rerun the pipeline
* this is because the pipeline pushes an action commit to master, which will then conflict with a rerun (expected)
* if there are failures (e.g. registry authentication) it is safer to create a new branch & PR from the master branch, and create a new PR for the managed publish to the registry
Expand Down
Loading