Skip to content

Commit 1effa11

Browse files
projectgusdpgeorge
authored andcommitted
CONTRIBUTING: Add extra explanation of "Publish packages for branch".
I hadn't used this feature for a while, and realised there's one confusing element of it not previously mentioned in the docs. Signed-off-by: Angus Gratton <angus@redyak.com.au>
1 parent 66fa62b commit 1effa11

File tree

1 file changed

+9
-4
lines changed

1 file changed

+9
-4
lines changed

Diff for: CONTRIBUTING.md

+9-4
Original file line numberDiff line numberDiff line change
@@ -102,15 +102,20 @@ Pages](https://docs.github.com/en/pages):
102102
"truthy" value).
103103
5. The settings for GitHub Actions and GitHub Pages features should not need to
104104
be changed from the repository defaults, unless you've explicitly disabled
105-
them.
105+
Actions or Pages in your fork.
106106

107107
The next time you push commits to a branch in your fork, GitHub Actions will run
108108
an additional step in the "Build All Packages" workflow named "Publish Packages
109-
for branch".
109+
for branch". This step runs in *your fork*, but if you open a pull request then
110+
this workflow is not shown in the Pull Request's "Checks". These run in the
111+
upstream repository. Navigate to your fork's Actions tab in order to see
112+
the additional "Publish Packages for branch" step.
110113

111114
Anyone can then install these packages as described under [Installing packages
112-
from forks](README.md#installing-packages-from-forks). The exact commands are also
113-
quoted in the GitHub Actions log for the "Publish Packages for branch" step.
115+
from forks](README.md#installing-packages-from-forks).
116+
117+
The exact command is also quoted in the GitHub Actions log in your fork's
118+
Actions for the "Publish Packages for branch" step of "Build All Packages".
114119

115120
#### Opting Back Out
116121

0 commit comments

Comments
 (0)