foster/forgejo-docs
0
0
Fork 0
mirror of https://codeberg.org/forgejo/docs.git synced 2024-11-21 17:36:59 -05:00
Code Issues Activity

previews are now available on forked pull requests as well

Browse source
This commit is contained in:
Earl Warren 2023-12-25 23:58:03 +01:00
parent 1caecddf18
commit 0538ec1a01
No known key found for this signature in database
GPG key ID: 0579CB2928A78A00
2 changed files with 1 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
.forgejo/workflows/pr.yml
View file

@ -1,7 +1,7 @@
name: pr name: pr
on: on:
pull_request: pull_request_target:
jobs: jobs:
preview: preview:

17
README.md
View file

@ -116,23 +116,6 @@ Such a feature branch can then be merged into multiple versions of the docs if a
In this case, the feature branch should usually be taken from the last common ancestor of all of the In this case, the feature branch should usually be taken from the last common ancestor of all of the
version branches into which it will potentially be merged. version branches into which it will potentially be merged.
If you have commit access to this repository, you should work on a temporary branch within this repository
with the `pr/` prefix and submit your pull request from there. Use the following commands to do it.
```sh
git clone git@codeberg.org:forgejo/docs ; cd docs
git checkout <target-branch>
git checkout -b pr/<short-pr-desc>
# Make the changes you want to submit
git add . ; git commit
git push -u origin pr/<short-pr-desc>
# Proceed to open your pull request
```
This is currently necessary due to technical limitations with Forgejo Actions. If you do not have commit
access, you may fork this repository and send a pull request the usual way, but a live preview of the
website will not be available.
#### Backports #### Backports
If a PR is meant to be backported to a stable branch, it must be If a PR is meant to be backported to a stable branch, it must be