tahoe-lafs/web-landing-page
4
1
Fork 1
Code Issues 6 Pull requests 3 Actions Activity

Support checks in forked repositories #35

Open
btlogy wants to merge 1 commit from btlogy/web-landing-page:34.ci-forks into main
pull from: btlogy/web-landing-page:34.ci-forks
merge into: tahoe-lafs:main
Conversation 3 Commits 1 Files changed 3 +3
3 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
.forgejo/workflows/jekyll.yaml
View file

@ -56,6 +56,7 @@ jobs:
jekyll build --verbose jekyll build --verbose
- name: Deploy Jekyll site - name: Deploy Jekyll site
id: deploy_site id: deploy_site
if: ${{ ! forge.event.pull_request.head.repo.fork }}
run: | run: |
if [ "${{ forge.ref }}" = 'refs/heads/main' ]; then if [ "${{ forge.ref }}" = 'refs/heads/main' ]; then
WEB_ROOT="${WEB_DIR}/live" WEB_ROOT="${WEB_DIR}/live"

1
.forgejo/workflows/jekyll_cleanup.yml
View file

@ -12,6 +12,7 @@ env:
WEB_CONTEXT: "/${{ forge.event.pull_request.number }}/" WEB_CONTEXT: "/${{ forge.event.pull_request.number }}/"
jobs: jobs:
jekyll_cleanup: jekyll_cleanup:
if: ${{ ! forge.event.pull_request.head.repo.fork }}
runs-on: ubuntu-22.04 runs-on: ubuntu-22.04
permissions: permissions:
pull-requests: read pull-requests: read

1
README.md
View file

@ -21,3 +21,4 @@ docker-compose up
We welcome contributions! Easiest is to open tickets or pull requests directly. If unsure, join the IRC or ask on the Tahoe-LAFS developer mailing list. We welcome contributions! Easiest is to open tickets or pull requests directly. If unsure, join the IRC or ask on the Tahoe-LAFS developer mailing list.
**Caveat**: because they need access to the repository secrets (e.g. SSH private key), the deployment step will be skipped on forked repositories. Which means preview sites will only be published from local branches pushed by collaborators with permissions to write in this repository.