You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+48-1Lines changed: 48 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -31,6 +31,39 @@ ALSO NOTE: github.com lets you create a pull request from the main branch, autom
31
31
32
32
> A code review (which happens with both the contributor and the reviewer present) is required for contributing.
33
33
34
+
## Pull Requests
35
+
36
+
### Upstream Testing
37
+
38
+
`linkml-runtime` is tightly coupled to upstream `linkml`,
39
+
so all pull requests have their changes tested by running the upstream tests
40
+
against the PR version of `linkml-runtime`.
41
+
42
+
In some circumstances, paired changes need to be made against *both*
43
+
`linkml` and `linkml-runtime`, where testing against the `main` branch
44
+
of `linkml` is insufficient.
45
+
46
+
When opening a pull request, you can specify that your PR needs to be
47
+
tested against a specific upstream branch and repository by specifying it
48
+
in the first two lines of your pull request like this:
49
+
50
+
> upstream_repo: my-cool-username/linkml
51
+
> upstream_branch: some-complicated-feature
52
+
>
53
+
> Hey everyone what up it's me your boy MC spongebob here with another banger
54
+
> ... (PR continues)
55
+
56
+
The order of the `upstream_repo` and `upstream_branch` tags doesn't matter,
57
+
but they must be on the first two lines of the pull request comment and separated with a colon.
58
+
59
+
Maintainers can also specify upstream branches to test against when
60
+
dispatching the `test-upstream` workflow manually via the GUI prompt.
61
+
62
+
Testing against an unverified upstream branch is not necessarily dangerous,
63
+
since the [input is stored as a variable first and not executed as untrusted code](https://docs.github.com/en/actions/security-for-github-actions/security-guides/security-hardening-for-github-actions#using-an-intermediate-environment-variable),
64
+
but maintainers should take care to verify that the upstream branch and repo
65
+
are correct and expected given the context of the PR.
0 commit comments