nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

You do not have permission to edit

rs232

I have been contributing to a project for year, literally years. All of a sudden about 3 months ago, I can click the Edit button on the target repo. I was always able to do so and as part of my modification create a PR online directly.

I have been ion talks with the repo owner and we tried everything we could see in the settings, still I can't edit files not create a PR from a fork. I'm defined with write access in the repo and other users that are not even defined can edit the file and send PR. So we are all puzzled on what the root cause is here.

Is there a list of troubleshooting steps I can go through to try to fix this?

Thanks

Accepted answers

All comments

Syahrul

G'day, @rs232

Welcome to the community!

That's an interesting issue. I can see you only have admin access to a forked repository. Is this the repository that you were having an issue editing?

If yes, can you navigate to the repository > Repository settings > Repository permissions and grab a screenshot so I can see the repository permission? This will help me identify if you have the correct permission to the repository or not.

Regards,
Syahrul

rs232

The repo I'm contributing to (and the Edit button on individual files directly on the target repo always worked (until 2/3 months ago) is this one:

https://bitbucket.org/pedro311/freshtomato-arm/src/arm-master

If you look in the commits, there were a number of PR I personally submitted using this very method:

- browse directly the target repo

- find the file and click edit

- save the modified file and create a PR as part of it.

The OP here is to indicate that for no apparent reason (the repo owner also investigated this and confirmed he absolutely changed nothing in the permissions) the Edit button is now greyed out.

P..S. I did try to fork and make the modification locally on my repo but:

- I deleted my historical fork of the main repo to try to have a fresh approach to this issue and go by exclusion

- I can't create a PR due to permission problems

- even if it would work... the Edit approach is priceless for little changes where e.g. we just correct the English

- It used to work it doesn't any more

- this, I'm reading on our support forum, is experienced by some other users but not all of them. When experienced, the issue is identical: the Edit button is greyed out.

Thanks

Syahrul

Hi there,

Thanks for sharing the details on the issue.

Based on my observation, you were not making any changes directly on the repository. Instead, they were made on a forked repository and then merged through PR creation.

For example PR #227, if you navigate to the source on the top, you'll see that the source comes from a fork repository rs232-/freshtomato-arm_2025-01-04--14-46-05--078805

That said, I noticed you were part of the repository in November last year but left the workspace earlier this year. So, if you have Read access to the repository, you can edit the source files directly from UI. However, it will not be edited directly on the repository; instead, it creates a fork and a PR to merge. This is mentioned in our documentations here, so you may need to request the repository owner to grant you reread access to the repository to allow you to edit the files directly on the UI.

I hope this helps.

Regards,
Syahrul

rs232

So to clarify:

- the original fork was deleted in an attempt to fix this permission issue

- When I delete a workplace I'm unable to recreate one with the very same name; e.g. my original workspace long time ago was rs232, when I deleted it back then I try to recreate it and was not allowed. Now rs232 is used but somebody else. The same applies to "rs232-" I deleted it yesterday in an attempt to fix once again the permission issue but could not recreate a workspace with the same name minutes after the original was deleted.

- As stated above, most of my PR are done from the source repo GUI using the Edit button. This applies also to the example commit you brought up. Once you go saving, the site asks you if you want to create a PR for the change. That's how I always operate for small changes. For big changes, I used to create PR from my own repo fork, but once again this is not what I have been doing lately and this is not what the OP refers to.

- I already confirmed that the repo owner changed nothing on his side.

- some users suffer from the same issue as mine (unable to Edit button greyed out) others don't. We couldn't identify a pattern.

I'll ask the repo owner if he can add his comments to his topic.

Thanks

pedro311

As the owner of the above repository, I can only say that the problems started a few months weeks (?) ago, for no reason. The repository has a public status and up until a certain point everything worked as it should: a registered user could make a pull request, or edit a file + pull request.

Right now it works for some users, but not for others. For example here: https://bitbucket.org/pedro311/freshtomato-arm/pull-requests/228 this user could add a PR without any problems, and he doesn't have any special permissions (and he shouldn't, given the repo settings). On the other hand, @rs232 can't do anything, even when I gave him READ access to the repo.

What's going on here?

Syahrul

Hey @rs232 & @pedro311

I've observed most of the merged PRs, and I can confirm that no direct edits have been made on the main repository. Most of the PRs that were merged originated from forked repositories. For example, PR 228 was raised from a forked repository located at https://bitbucket.org/mobrembski/freshtomato-arm/src/arm-master/.

I can also confirm that making edits online requires write access to the repository. If a user does not have this permission, they must fork the repository and make edits or updates on their forked version. They would then raise a PR to the upstream repository to be reviewed and merged.

I believe @rs232 behavior might be because he was editing from a forked repository rather than the original repository. If he was able to edit the original repository before, it was likely because he was granted write access back in November of last year.

As for @rs232 you mentioned about some folders have an edit button enabled, did you try to click that and edit anything to see if it's possible?

Update:

I forgot to mention that I am also checking this internally to see if this was a past experience where I am unaware of. So please bear with me, I'll update you folks once I have anything.

Regards,
Syahrul

rs232

I'm sorry, but I disagree with most of what you said. I appreciate you are trying to help, but if I tell you that most of my commits where PR generated from a direct [Edit] (via Edit button) of the source repo, you either believe me or not. And if you don't we can stop the conversation here. I'm not sure why you are insisting on telling me I did my PR from my fork, I guess you are just looking at the wrong place.

Sure, there has been "some" (very few) PR generated from my own fork in the past, but almost nothing compared to the direct edit on the source Repo.

This PR below was 100% certainly done via the Edit button on the source repo.

https://bitbucket.org/pedro311/freshtomato-arm/pull-requests/220/diff

So please let's stop challenging what it is reported here. The issue is simple, the Edit button is greyed out... sometimes only! When this happens, we can confirm absolutely nothing changed on mine or the repo owner side.

Look at this file

https://bitbucket.org/pedro311/freshtomato-arm/src/arm-master/release/src-rt-6.x.4708/router/www/advanced-dhcpdns.asp

This morning, I had the [Edit] available for it, but I didn't click it. This afternoon I simply reloaded the page and the [Edit] is greyed out.

Everything suggests you do have some issues at Bitbucket that you'd better off investigating. Once again, I'm not the only user affected, but at the same time, not all the users are affected. Random is a good way to express the issue.

Thanks

Syahrul

Hey @rs232

Thank you for the update, and I sincerely apologize for any confusion caused.

I have discussed this issue internally and discovered that there is likely a bug on our end. Typically, a public repository should grant Read access to all logged-in users, allowing them to click the Edit button.

Users should be able to make changes and commit them when they click the Edit button. Behind the scenes, this process involves creating a fork of the repository. Citing commit automatically raises a pull request from the forked repository to the upstream repository. I apologize for any misunderstanding about this behavior.

We've reported this as a bug, and I recommend monitoring its progress by voting and watching it here: https://jira.atlassian.com/browse/BCLOUD-23536

As a temporary workaround, you can consider manually forking the repository until the issue is fixed.

Regards,
Syahrul

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud

permission

edit