Not able to do a PULL REQUEST

[Gopi Tholeti]

Hi team,

One of my team members is not able to do a Pull request.

In our practice, we have a user group and add team members with read access.

Intention:
When members want to do code changes, by default they can't commit and should check the create a pull request option and a Pull request should be created.

This approach was working and no issues till now. 

I recently observed that the new team members were given Read access to the repo, but they were not able to create a pull request.

Can someone help me understand what could be the problem?

Thanks

[Theodora Boudale]

Hi Gopi,

Thank you for reaching out.

If a user has read-only access to a repo, then they need to first create a fork of the repo, make changes in the fork, and then raise a PR from the fork to the parent repo.

I would need some additional details so I can better help you:

1. What are the exact steps that these team members follow? (detailed steps, like what page they are on, what option they click each step of the way, etc)
2. What kind of error do they get that prevents them from opening the pull request? A screenshot would be helpful (please make sure that any private data in the screenshot is blurred, prior to sharing)

You could also ask one of the affected team members to post a reply here with this info.

Kind regards,
Theodora

[Gopi Tholeti]

Hi Theodora,

Thanks for your response.

Working scenario for all members:
Members will make a change to file in a repo and select Create a pull request for this change and commit changes. Then reviewer will review and merge the changes accordingly.

Note: Members got Read access for that specific repo by adding them to the group at repo level permission. Only selected reviewers got write access. 



Problem:
Recently, a new team member joined, we added them to the same group and they got read access. 

When they tried to commit changes, it threw an error saying " We had trouble creating your fork."

What could be the issue with this?

Thanks

[Theodora Boudale]

Hi Gopi,

Thank you for the details.

This looks like it may be a bug. I see a bug report for that error message that was fixed in March 2023, but there might be a regression:

https://jira.atlassian.com/browse/BCLOUD-22516

Workaround:

Could you ask this team member to manually create a fork for the repo, make changes in the fork, and then create a pull request?

While viewing the Source page of the repo on Bitbucket website, if the user selects the 3 dots next to the Clone button, they should see the option Fork this repository.

Details for investigation:

I would also like to ask if you could provide some more details to understand what may be causing this.

When your team member has this Commit changes dialog open, can they do the following?

1. Open Developer tools on their browser
2. After they open Developer tools, click the Commit button to reproduce the error
3. Then, select the Network tab and look for any requests with 4xx or 5xx error
4. Then select each of these requests and click the Response on the right panel

Could you please let me know what is the Response for each request with 4xx or 5xx error?

Kind regards,
Theodora

[Gopi Tholeti]

Hi Theodora,

At the moment, I asked them to fork and do a pull request. And that approach is working.

I can share more details for investigation.

Thanks

[Theodora Boudale]

Hi Gopi,

Thank you for the update, it's good to hear that the workaround works for your team member.

I went ahead and reopened the public bug report I shared earlier. Please feel free to share additional details when you have some time and I will include them in the bug report.

Kind regards,
Theodora