Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
polkadot-sdk
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
parity
Mirrored projects
polkadot-sdk
Commits
8614dc0e
Unverified
Commit
8614dc0e
authored
6 months ago
by
Bastian Köcher
Committed by
GitHub
6 months ago
Browse files
Options
Downloads
Patches
Plain Diff
Always amend to the same commit for gh-pages (#5909)
parent
3cf83ca8
No related merge requests found
Pipeline
#499652
waiting for manual action with stages
in 1 hour, 1 minute, and 24 seconds
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
.gitlab/pipeline/publish.yml
+1
-1
1 addition, 1 deletion
.gitlab/pipeline/publish.yml
with
1 addition
and
1 deletion
.gitlab/pipeline/publish.yml
+
1
−
1
View file @
8614dc0e
...
...
@@ -54,7 +54,7 @@ publish-rustdoc:
# This causes GitLab to exit immediately and marks this job failed.
# We don't want to mark the entire job failed if there's nothing to
# publish though, hence the `|| true`.
-
git commit -m "___Updated docs
for ${CI_COMMIT_REF_NAME}___
" ||
-
git commit
--amend
-m "___Updated docs" ||
echo "___Nothing to commit___"
-
git push origin gh-pages --force
# artificial sleep to publish gh-pages
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment