Permissions for dependencies for issues

[LukeOwlclaw]

• 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 #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?

[lunny]

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

[LukeOwlclaw]

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.

[stale]

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.

[LukeOwlclaw]

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.