mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2026-03-25 14:33:05 -04:00
35b872f383
Adds a user interface for creating repo-specific access tokens (#11311). When the new option "Specific repositories" is selected, a search option appears. Each repository in the search result has an "Add" button to include it on the access token, and once included, a repository can be removed with the "Remove" button. This is a JS-free form. ## Checklist The [contributor guide](https://forgejo.org/docs/next/contributor/) 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). ### Tests for Go changes (can be removed for JavaScript changes) - I added test coverage for Go changes... - [x] in their respective `*_test.go` for unit tests. - [ ] in the `tests/integration` directory if it involves interactions with a live Forgejo server. - I ran... - [x] `make pr-go` before pushing ### Tests for JavaScript changes - I added test coverage for JavaScript changes... - [ ] in `web_src/js/*.test.js` if it can be unit tested. - [x] 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)). - Technically there are no "JavaScript changes" in this PR, but e2e tests were added for browser interaction testing. ### Documentation - [ ] I created a pull request [to the documentation](https://codeberg.org/forgejo/docs) to explain to Forgejo users how to use this change. - TODO: planning to create documentation in https://forgejo.org/docs/next/user/token-scope/; there is none for public only tokens but I think this seems like a good place to add both. - [ ] I did not document these changes and I do not expect someone else to do it. ### Release notes - [x] This change will be noticed by a Forgejo user or admin (feature, bug fix, performance, etc.). I suggest to include a release note for this change. - [ ] This change is not visible to a Forgejo user or admin (refactor, dependency upgrade, etc.). I think there is no need to add a release note for this change. Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/11696 Reviewed-by: Andreas Ahlenstorf <aahlenst@noreply.codeberg.org> Co-authored-by: Mathieu Fenniak <mathieu@fenniak.net> Co-committed-by: Mathieu Fenniak <mathieu@fenniak.net> |
||
|---|---|---|
| .. | ||
| fixtures/TestFindRepoAttachmentsByUUID | ||
| TestGetUserForkLax | ||
| TestGetUserForkLaxWithTwoChoices | ||
| TestSearchRepositoryIDsByCondition | ||
| archive_download_count.go | ||
| archive_download_count_test.go | ||
| archiver.go | ||
| attachment.go | ||
| attachment_test.go | ||
| authz.go | ||
| avatar.go | ||
| collaboration.go | ||
| collaboration_test.go | ||
| following_repo.go | ||
| following_repo_test.go | ||
| fork.go | ||
| fork_test.go | ||
| git.go | ||
| issue.go | ||
| language_stats.go | ||
| language_stats_test.go | ||
| main_test.go | ||
| mirror.go | ||
| moderation.go | ||
| moderation_test.go | ||
| pushmirror.go | ||
| pushmirror_test.go | ||
| redirect.go | ||
| redirect_test.go | ||
| release.go | ||
| release_list.go | ||
| release_list_test.go | ||
| release_test.go | ||
| repo.go | ||
| repo_flags.go | ||
| repo_flags_test.go | ||
| repo_indexer.go | ||
| repo_list.go | ||
| repo_list_test.go | ||
| repo_repository.go | ||
| repo_test.go | ||
| repo_unit.go | ||
| repo_unit_test.go | ||
| search.go | ||
| star.go | ||
| star_test.go | ||
| topic.go | ||
| topic_test.go | ||
| update.go | ||
| update_test.go | ||
| upload.go | ||
| user_repo.go | ||
| user_repo_test.go | ||
| watch.go | ||
| watch_test.go | ||
| wiki.go | ||
| wiki_test.go | ||