oppi.li / perf-test
loading up the forgejo repo on tangled to test page performance
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

docs: add a PR checklist template (#4564)

Manual testing of this template can be done with the new playground created for that purpose, see https://code.forgejo.org/forgejo/pr-and-issue-templates/pulls/19.

![image](/attachments/1ee36ae1-669f-47d8-8307-9734faa0dc2a)

## Testing instructions

* Fork https://code.forgejo.org/forgejo/pr-and-issue-templates
* Create a pull request against https://code.forgejo.org/forgejo/pr-and-issue-templates
* See that the commit message is on top and the checklist below it

---

Use cases:

* https://codeberg.org/forgejo/forgejo/pulls/4553
* https://codeberg.org/forgejo/forgejo/pulls/4554

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/4564
Reviewed-by: 0ko <0ko@noreply.codeberg.org>
Reviewed-by: twenty-panda <twenty-panda@noreply.codeberg.org>
Reviewed-by: thefox <thefox@noreply.codeberg.org>
Co-authored-by: Earl Warren <contact@earl-warren.org>
Co-committed-by: Earl Warren <contact@earl-warren.org>

authored by

Earl Warren
Earl Warren and committed by
Earl Warren 7511ae53 5a41d902

+33 -13
+33
.forgejo/pull_request_template.md
··· 1 + --- 2 + 3 + name: "Pull Request Template" 4 + about: "Template for all Pull Requests" 5 + labels: 6 + 7 + - test/needed 8 + 9 + --- 10 + 11 + ## Checklist 12 + 13 + The [developer guide](https://forgejo.org/docs/next/developer/) contains information that will be helpful to first time contributors. There also are a few [conditions for merging Pull Requests in Forgejo repositories](https://codeberg.org/forgejo/governance/src/branch/main/PullRequestsAgreement.md). You are also welcome to join the [Forgejo development chatroom](https://matrix.to/#/#forgejo-development:matrix.org). 14 + 15 + ### Tests 16 + 17 + - I added test coverage for Go changes... 18 + - [ ] in their respective `*_test.go` for unit tests. 19 + - [ ] in the `tests/integration` directory if it involves interactions with a live Forgejo server. 20 + - I added test coverage for JavaScript changes... 21 + - [ ] in `web_src/js/*.test.js` if it can be unit tested. 22 + - [ ] in `tests/e2e/*.test.e2e.js` if it requires interactions with a live Forgejo server (see also the [developer guide for JavaScript testing](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/tests/e2e/README.md#end-to-end-tests)). 23 + 24 + ### Documentation 25 + 26 + - [ ] I created a pull request [to the documentation](https://codeberg.org/forgejo/docs) to explain to Forgejo users how to use this change. 27 + - [ ] I did not document these changes and I do not expect someone else to do it. 28 + 29 + ### Release notes 30 + 31 + - [ ] I do not want this change to show in the release notes. 32 + - [ ] I want the title to show in the release notes with a link to this pull request. 33 + - [ ] I want the content of the `release-notes/<pull request number>.md` to be be used for the release notes instead of the title.
.gitea/issue_template/bug-report-ui.yaml .forgejo/issue_template/bug-report-ui.yaml
.gitea/issue_template/bug-report.yaml .forgejo/issue_template/bug-report.yaml
.gitea/issue_template/config.yml .forgejo/issue_template/config.yml
.gitea/issue_template/feature-request.yaml .forgejo/issue_template/feature-request.yaml
-13
.gitea/pull_request_template.md
··· 1 - --- 2 - 3 - name: "Pull Request Template" 4 - about: "Template for all Pull Requests" 5 - labels: 6 - 7 - - test/needed 8 - 9 - --- 10 - <!-- 11 - Before submitting a PR, please read the contributing guidelines: 12 - https://codeberg.org/forgejo/forgejo/src/branch/forgejo/CONTRIBUTING.md 13 - -->