Skip to content

user's permissions on Issues/PRs #100

@marusinm

Description

@marusinm

Updated by @lachmanfrantisek :

We have a lot of methods related to the permissions (e.g. who can merge/close,..)

It's not consistent, let's clean that!

Feel free to solve this in smaller parts. Just write on what you are going to work...

AC:

The progress is tracked in the following tables. (Any update in the comments is appreciated.)

Project who_can_close_issue() -> Set[str] who_can_merge_pr() -> Set[str] can_close_issue(username: str) -> bool can_merge_pr(username: str) -> bool
abstract 👍 👍 ❗ deprecate the Issue argument
base nothing nothing implement here implement here
Github ? ? ? ?
GitLab ? ? ? ?
Pagure ? ? ? ?
Issue who_can_close() -> Set[str] can_close(username: str) -> bool
abstract implement here 👍
base nothing 👍
Github ? nothing
GitLab ? nothing
Pagure ? nothing
PullRequest who_can_close() -> Set[str] who_can_merge() -> Set[str] can_close(username: str) -> bool can_merge(username: str) -> bool
abstract ? ? ? ?
base nothing nothing implement here implement here
Github ? ? ? ?
GitLab ? ? ? ?
Pagure ? ? ? ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/githubGitHub-forge relatedarea/gitlabGitLab-forge relatedevents/HacktoberfestParticipation in Hacktoberfestgood-first-issueGood for newcomerskind/featureA request, idea, or new functionalitykind/technical-debtConsequences of previous decisionspagureRelated to Pagure implementation.

    Type

    No type

    Projects

    Status

    backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions