Skip to content

Private issues and pull requests on public repositories #4274

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.

Sign up for GitHub

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

Jump to bottom
Closed
lunny opened this issue Jun 19, 2018 · 2 comments
Closed

Private issues and pull requests on public repositories #4274

lunny opened this issue Jun 19, 2018 · 2 comments
Labels
issue/duplicate The issue has already been reported.

Comments

@lunny
Copy link
Member

lunny commented Jun 19, 2018

I would like the repository writer could create private issues and pull requests which only could be visited by repository's owners, collaborations and other who have read/write permisstion to the repository. That's very useful when there are some security reports or pull requests.
@lunny lunny added type/proposal The new feature has not been accepted yet but needs to be discussed first. type/feature Completely new functionality. Can only be merged if feature freeze is not active. labels Jun 19, 2018
@kolaente
Copy link
Member

possible duplicate of #3217 ?

@lunny lunny added issue/duplicate The issue has already been reported. and removed type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. labels Jun 20, 2018
@lunny
Copy link
Member Author

lunny commented Jun 20, 2018

@kolaente right.

@lunny lunny closed this as completed Jun 20, 2018
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
project-mirrors-bot-tu bot pushed a commit to project-mirrors/forgejo-as-gitea-fork that referenced this issue Jan 23, 2025
@ExplodingDragon
Fix: database not updated when using git push --tags --force (go-gi…
4cd425a 
…tea#5319)

Closes go-gitea#4274

link: go-gitea#32040

### Release notes

- [ ] I do not want this change to show in the release notes.

<!--start release-notes-assistant-->

## Draft release notes
<!--URL:https://codeberg.org/forgejo/forgejo-->
- Bug fixes
  - [PR](https://codeberg.org/forgejo/forgejo/pulls/5319): <!--number 5319 --><!--line 0 --><!--description Rml4OiBkYXRhYmFzZSBub3QgdXBkYXRlZCB3aGVuIHVzaW5nIGBnaXQgcHVzaCAtLXRhZ3MgLS1mb3JjZWA=-->Fix: database not updated when using `git push --tags --force`<!--description-->
<!--end release-notes-assistant-->

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/5319
Reviewed-by: Otto <[email protected]>
Co-authored-by: Exploding Dragon <[email protected]>
Co-committed-by: Exploding Dragon <[email protected]>
(cherry picked from commit a6508f5)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
issue/duplicate The issue has already been reported.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lunny @kolaente