Can't seem to get the permission I need to push to an organisation repo

[SimonBD1]

Select Topic Area

Question

Body

Hey everyone

I have an organisation with a few fellow students, and we are in the middle of a project. The problem is that even though we are all set as admins on the org and repo, only some of us are able to push to it, even if the person who is pushing created that branch. What could be a solution to our problem? We tried to look through the orgs settings and the repository settings, but could not find the answers ourselves. We also tried to generate keys to login to our IDE, but still no progress.

thanks for the help in advance! :)

[rnldvrgl]

Can you check the following for troubleshooting, There are several reasons for this issue and I hope this will helps:

Check Repository Settings:
    Ensure that the repository settings have not restricted specific users or teams from pushing to the repository. To do this, go to the repository's settings, then click on "Manage access" or "Collaborators & teams" and review the permissions for each user or team.

Branch Protection Rules:
    It's possible that branch protection rules have been set up for the repository, which can restrict who can push to specific branches. Check if there are branch protection rules in place. To do this, go to the repository settings, then navigate to "Branches" or "Branch protection rules." Review the rules and make sure they allow the necessary users to push to the branch.

User Permissions:
    Verify that all users who are experiencing issues have the necessary permissions. While they may be admins on the organization or repo, it's possible that their specific permissions on the branch in question are limited. Make sure they have "Write" or "Admin" access to the branch.

SSH Keys and Authentication:
    Confirm that the users with push issues are using the correct SSH keys or authentication method when interacting with the repository. Make sure they have added their SSH keys to their GitHub accounts and are using the correct email addresses for committing to the repository.

Check for Credential Issues:
    Sometimes, credential issues in the local Git configuration can cause problems. Ensure that users have their Git configurations properly set up, including their username and email address matching their GitHub account.

Collaborator vs. Team Member:
    Double-check if the users who can't push are collaborators or team members. Sometimes, organization-level permissions don't grant the same access to individual repositories. Make sure they are added as collaborators to the specific repository if necessary.

Review Audit Logs:
    GitHub provides audit logs that can help you track actions performed by users in the organization. Check the audit logs for any relevant events or permission changes that may have affected the users in question.

Contact GitHub Support:
    If you've gone through the above steps and still can't identify the issue, it may be worth reaching out to GitHub Support for assistance. They can help investigate and resolve permissions-related problems.

[SimonBD1]

Thanks for writing your feedback, We did check every marker in The settings menu, and everything looked fine, all roles and settings should of had let us push to our repositories, but we couldnt for some then unknown reason.

We did however manage to find a solution. In the organisations settings we went to "third-party access" and adjusted our "OAuth application policy"-settings, and that worked out, we are now all able to work with the repository how we want.

[swabhs]

Hi there, I'm facing a similar issue. Exactly what changes did you make? I have set mine to "No Restrictions" and yet I'm unable to push any changes to the repository even though I'm the owner and admin...

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬