Permissions for dependencies for issues #3946

New Issue

2025-11-02T05:31:24-06:00

GiteaMirror commented

2025-11-02 05:31:24 -06:00

Originally created by @LukeOwlclaw on GitHub (Sep 13, 2019).

Gitea version (or commit ref): 1.9.3
Operating system: Win
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes
- No
- Not relevant

Description

Since https://github.com/go-gitea/gitea/issues/2196 we have 'Dependencies for issues'. Awesome! But users need write permission to use it. I find that problematic: When I add a PR which should be merged after another (of my) PR, I cannot configure that.

Bug or feature?

Originally created by @LukeOwlclaw on GitHub (Sep 13, 2019).   - Gitea version (or commit ref): 1.9.3 - Operating system: Win - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [X] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes - [ ] No - [ ] Not relevant ## Description Since https://github.com/go-gitea/gitea/issues/2196 we have 'Dependencies for issues'. Awesome! But users need write permission to use it. I find that problematic: When I add a PR which should be merged after another (of my) PR, I cannot configure that. Bug or feature?

GiteaMirror added the type/proposal issue/confirmed labels 2025-11-02 05:31:24 -06:00

GiteaMirror commented

2025-11-02 05:31:24 -06:00

@lunny commented on GitHub (Sep 13, 2019):

I think we haven't check that one PR could not be merged if it depends another open PR.

@lunny commented on GitHub (Sep 13, 2019): I think we haven't check that one PR could not be merged if it depends another open PR.

GiteaMirror commented

2025-11-02 05:31:25 -06:00

@LukeOwlclaw commented on GitHub (Sep 16, 2019):

Okay, I see what you mean (I mixed too things). In this issue I am just concerned about the permission a user needs to have to set a dependency. Currently it is 'write', I'd like it to be 'read'. Or may be even better: 'write' but also allow the creator of the PR to set a dependency.

@LukeOwlclaw commented on GitHub (Sep 16, 2019): Okay, I see what you mean (I mixed too things). In this issue I am just concerned about the permission a user needs to have to set a dependency. Currently it is 'write', I'd like it to be 'read'. Or may be even better: 'write' but also allow the creator of the PR to set a dependency.

GiteaMirror commented

2025-11-02 05:31:25 -06:00

@stale[bot] commented on GitHub (Nov 15, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Nov 15, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:31:25 -06:00

@LukeOwlclaw commented on GitHub (Nov 22, 2019):

Same problem applies for setting an "Assignee" for an issue. I can only do that when I have write permissions for the repo. Again my question: Is this intentionally design or did it just "happen"?
I'd love to have some options to set these meta data tags without being able to write to the repo.

@LukeOwlclaw commented on GitHub (Nov 22, 2019): Same problem applies for setting an "Assignee" for an issue. I can only do that when I have write permissions for the repo. Again my question: Is this intentionally design or did it just "happen"? I'd love to have some options to set these meta data tags without being able to write to the repo.

GiteaMirror referenced this issue

2025-11-02 12:27:52 -06:00

[PR #3946] [MERGED] Fix comments in config1 #17159

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#3946