Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explained where create issue/PR template #29035

Merged
merged 3 commits into from
Feb 19, 2024
Merged

Conversation

camlafit
Copy link
Contributor

@camlafit camlafit commented Feb 3, 2024

For some user (as me), documentation lack of precision about where to store issue/pr template.

I propose an enhancement about this point. With bold exergue and precision about server itself.

I've found some user with same interrogation as : https://forum.gitea.com/t/issue-template-directory/3328

For some user (as me), documentation lack of precision about where to store issue/pr template.

I propose an enhancement about this point. With bold exergue and precision about server itself.
@GiteaBot GiteaBot added this to the 1.21.6 milestone Feb 3, 2024
@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Feb 3, 2024
@pull-request-size pull-request-size bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Feb 3, 2024
@camlafit camlafit changed the title Explained where create template Explained where create issue/PR template Feb 3, 2024
@techknowlogick techknowlogick added the backport/v1.21 This PR should be backported to Gitea 1.21 label Feb 3, 2024
@GiteaBot GiteaBot removed the backport/v1.21 This PR should be backported to Gitea 1.21 label Feb 3, 2024
@GiteaBot GiteaBot added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Feb 4, 2024
@camlafit camlafit changed the base branch from release/v1.21 to main February 4, 2024 09:37
@camlafit camlafit changed the base branch from main to release/v1.21 February 4, 2024 09:37
@camlafit
Copy link
Contributor Author

camlafit commented Feb 4, 2024

Hello

My bad I've not check base branch, I've edited from web ui and forgotten to rebase over main branch.

Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
Default branch is better to use
@6543 6543 added the frontport/main This PR is not targeting the main branch. Still, its changes should also be added there label Feb 19, 2024
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Feb 19, 2024
@6543 6543 merged commit 5b8b22b into go-gitea:release/v1.21 Feb 19, 2024
27 checks passed
@camlafit camlafit deleted the patch-2 branch February 19, 2024 15:33
6543 added a commit to 6543-forks/gitea that referenced this pull request Feb 19, 2024
For some user (as me), documentation lack of precision about where to
store issue/pr template.

I propose an enhancement about this point. With bold exergue and
precision about server itself.

I've found some user with same interrogation as :
https://forum.gitea.com/t/issue-template-directory/3328

---------

Co-authored-by: 6543 <6543@obermui.de>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
@6543 6543 added the frontport/done The frontport PR has been created label Feb 19, 2024
@6543
Copy link
Member

6543 commented Feb 19, 2024

-> #29266

jolheiser pushed a commit that referenced this pull request Feb 20, 2024
For some user (as me), documentation lack of precision about where to
store issue/pr template.

I propose an enhancement about this point. With bold exergue and
precision about server itself.

I've found some user with same interrogation as :
https://forum.gitea.com/t/issue-template-directory/3328

---------

Co-authored-by: Km <cam.lafit@azerttyu.net>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
zjjhot added a commit to zjjhot/gitea that referenced this pull request Feb 22, 2024
* giteaofficial/main: (32 commits)
  [skip ci] Updated translations via Crowdin
  Prevent double use of `git cat-file` session. (go-gitea#29298)
  Revert go-gitea#28753 because UI broken. (go-gitea#29293)
  Fix error display when merging PRs (go-gitea#29288)
  Refactor markup rendering to accept general "protocol:" prefix (go-gitea#29276)
  Remove jQuery from the installation page (go-gitea#29284)
  Always write proc-receive hook for all git versions (go-gitea#29287)
  Do not use `ctx.Doer` when reset password (go-gitea#29289)
  Update Discord logo (go-gitea#29285)
  [skip ci] Updated translations via Crowdin
  Remove jQuery .map() and enable eslint rules for it (go-gitea#29272)
  Explained where create issue/PR template (go-gitea#29035) (go-gitea#29266)
  Remove jQuery from repo wiki creation page (go-gitea#29271)
  Do not show delete button when time tracker is disabled (go-gitea#29257)
  Left align the input labels for the link account page (go-gitea#29255)
  [skip ci] Updated translations via Crowdin
  Remove jQuery from the repo migration form (go-gitea#29229)
  Fix content size does not match error when uploading lfs file (go-gitea#29259)
  Workaround to clean up old reviews on creating a new one (go-gitea#28554)
  Deduplicate translations for contributors graph (go-gitea#29256)
  ...
Copy link

Automatically locked because of our CONTRIBUTING guidelines

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
frontport/done The frontport PR has been created frontport/main This PR is not targeting the main branch. Still, its changes should also be added there lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. modifies/docs size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants