Woodpecker CI: Reimplement Gitlab api docs deployment pipeline #5

Open
phnt wants to merge 1 commit from woodpecker-ci into master
Owner
  • new secrets (all same contents as on Gitlab):
    • pleroma-ci-docs-host-key
    • pleroma-ci-docs-ssh-port
    • pleroma-ci-docs-priv-key
    • pleroma-ci-docs-host-location (repo specific, docs uses same secret name)
  • Deployments need to be enabled for this repository for the trigger in pleroma/pleroma to work (pleroma/pleroma!7928)
* new secrets (all same contents as on Gitlab): - pleroma-ci-docs-host-key - pleroma-ci-docs-ssh-port - pleroma-ci-docs-priv-key - pleroma-ci-docs-host-location (**repo specific, docs uses same secret name**) * Deployments need to be enabled for this repository for the trigger in pleroma/pleroma to work (pleroma/pleroma!7928)
Author
Owner

Uploaded a spec.json from Pleroma 2.10.2 as a package, so this can be merged before the MR in pleroma/pleroma

Uploaded a `spec.json` from Pleroma 2.10.2 as a package, so this can be merged before the MR in pleroma/pleroma
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin woodpecker-ci:woodpecker-ci
git switch woodpecker-ci

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master
git merge --no-ff woodpecker-ci
git switch woodpecker-ci
git rebase master
git switch master
git merge --ff-only woodpecker-ci
git switch woodpecker-ci
git rebase master
git switch master
git merge --no-ff woodpecker-ci
git switch master
git merge --squash woodpecker-ci
git switch master
git merge --ff-only woodpecker-ci
git switch master
git merge woodpecker-ci
git push origin master
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pleroma/api-docs!5
No description provided.