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

Disable commits and file changes tab if user has no code unit permission #32264

Open
yp05327 opened this issue Oct 15, 2024 · 7 comments
Open
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@yp05327
Copy link
Contributor

yp05327 commented Oct 15, 2024

Feature Description

Thanks @hakito's issue #32253.
There's another issue mentioned in the origin issue.
And you can also check the comment here: #32254 (comment)

updated:
And the review comment which can see the code changes.
image

Screenshots

No response

@yp05327 yp05327 added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Oct 15, 2024
@lunny
Copy link
Member

lunny commented Oct 16, 2024

Pull request is a whole feature, I don't think it's meaningful to disable these two tabs. I don't know how the pull request works for the end user if there is no commit history and changed files.

@wxiaoguang
Copy link
Contributor

It seems that this discussion doesn't get interests, and I do not see any benefit to make any change.

@wxiaoguang wxiaoguang added the issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail label Oct 21, 2024
@hakito
Copy link
Contributor

hakito commented Oct 21, 2024

Actually for our setup it would be good to have access to PR without access to the commits and file changes.

We are doing branch based development. When a feature has been completed, we create a PR. In the PR we refer to the issues which are implemented on the branch.

The Product Owner reviews the branch builds and therefore needs to know which issues have been implemented on the branch/PR. He then approves the issues or requests changes.

But he shouldn't have access to the code parts.

@lunny
Copy link
Member

lunny commented Oct 21, 2024

Actually for our setup it would be good to have access to PR without access to the commits and file changes.

We are doing branch based development. When a feature has been completed, we create a PR. In the PR we refer to the issues which are implemented on the branch.

The Product Owner reviews the branch builds and therefore needs to know which issues have been implemented on the branch/PR. He then approves the issues or requests changes.

But he shouldn't have access to the code parts.

Sounds a bit reasonable. But there is already a pull request comment in this issue. Maybe that is enough?

@yp05327
Copy link
Contributor Author

yp05327 commented Oct 21, 2024

He then approves the issues or requests changes.

Does this mean approve the PR or request changes feature of Gitea?
image
Or just mean approve the work? e.g. It is ok to work on this issue/PR, and the code review is not related.
As approve/require changes need code write permission, I think we need to confirm it.

@hakito
Copy link
Contributor

hakito commented Oct 21, 2024

It just means approve the work. We have a code review after the Product Owner approved the changes. During this review the actual approval of the PR occurs.

@yp05327
Copy link
Contributor Author

yp05327 commented Oct 22, 2024

#32299 (comment)
mark

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue/needs-feedback For bugs, we need more details. For features, the feature must be described in more detail type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

4 participants