Codeberg/Community
54
325
Fork
You've already forked Community
12

Editing (reviewing) PR locally, commit and push it back. Algorithm. #2271

Closed
opened 2025年12月24日 06:54:47 +01:00 by anametologin · 4 comments

Comment

I'm new on Codeberg and ran into a problem.
I have repository: https://codeberg.org/anametologin/Krohnkite
I have PR: PR

  1. I fetch it to edit(review, add) locally:
    git fetch origin $"pull/4/head:pr_4";
    git checkout $"pr_4"

  2. I change, add and commit:
    git add .
    git commit --message "I fixed PR_4"

  3. I want push it back
    git remote add jbeaurivage git@codeberg.org:jbeaurivage/Krohnkite.git
    git push jbeaurivage HEAD:sole-window-output-override

  4. I received:
    remote: Forgejo: User permission denied for writing. To codeberg.org:jbeaurivage/Krohnkite.git

ssh git@codeberg.org has output:
Hi there, anametologin! You've successfully authenticated with the key named pc-name, but Forgejo does not provide shell access.

Please help me figure out what I'm doing wrong.

### Comment I'm new on Codeberg and ran into a problem. I have repository: https://codeberg.org/anametologin/Krohnkite I have PR: [PR](https://codeberg.org/anametologin/Krohnkite/pulls/4) 1. I fetch it to edit(review, add) locally: `git fetch origin $"pull/4/head:pr_4";` `git checkout $"pr_4"` 2. I change, add and commit: `git add .` `git commit --message "I fixed PR_4"` 3. I want push it back `git remote add jbeaurivage git@codeberg.org:jbeaurivage/Krohnkite.git` `git push jbeaurivage HEAD:sole-window-output-override` 4. I received: `remote: Forgejo: User permission denied for writing. To codeberg.org:jbeaurivage/Krohnkite.git ` `ssh git@codeberg.org` has output: `Hi there, anametologin! You've successfully authenticated with the key named pc-name, but Forgejo does not provide shell access.` Please help me figure out what I'm doing wrong.

I have pushed successfully after PR creator grant me the write permissions.

I don't quite understand, should I ask every PR creator to give me the rights?

I have pushed successfully after PR creator grant me the write permissions. I don't quite understand, should I ask every PR creator to give me the rights?

I don't seem to know what is wrong, but just use this if you keep seeing the error:
git remote add origin https://USERNAME:PAT_TOKEN@codeberg.org/USERNAME/REPO

I don't seem to know what is wrong, but just use this if you keep seeing the error: `git remote add origin https://USERNAME:PAT_TOKEN@codeberg.org/USERNAME/REPO`

The pull request creator did not check the "Allow edits from maintainers" option (or unchecked it if this is enabled by default).

The pull request creator did not check the "Allow edits from maintainers" option (or unchecked it if this is enabled by default).

The pull request creator did not check the "Allow edits from maintainers" option (or unchecked it if this is enabled by default).

Thank you, it seems you are right.

> The pull request creator did not check the "Allow edits from maintainers" option (or unchecked it if this is enabled by default). Thank you, it seems you are right.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2271
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?