github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Not able to push code #2332

New Issue
Closed
opened 2025-11-02 04:33:04 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 04:33:04 -06:00
Owner
Copy Link

Originally created by @vbose1 on GitHub (Sep 14, 2018).

  • Gitea version (or commit ref):
  • Git version:
  • Operating system:
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Not able to push code when repository is created under organization. When I transfer repository on user then I can able to push.

error message as below

Pushing development
Remote: User permission denied
Error encountered while pushing to the remote repository: Git failed with a fatal error.
unable to access 'http://xxx.xxx.xxx.xxx:3000/xxxx/xxxxxxx.git/': The requested URL returned error: 403
...

Originally created by @vbose1 on GitHub (Sep 14, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): - Git version: - Operating system: - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [X] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [X] Not relevant - Log gist: ## Description Not able to push code when repository is created under organization. When I transfer repository on user then I can able to push. error message as below Pushing development Remote: User permission denied Error encountered while pushing to the remote repository: Git failed with a fatal error. unable to access 'http://xxx.xxx.xxx.xxx:3000/xxxx/xxxxxxx.git/': The requested URL returned error: 403 ...
GiteaMirror added the type/question label 2025-11-02 04:33:04 -06:00
GiteaMirror commented 2025-11-02 04:33:05 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Sep 14, 2018):

Does user has rights for that organization repository?

@lafriks commented on GitHub (Sep 14, 2018): Does user has rights for that organization repository?
GiteaMirror commented 2025-11-02 04:33:05 -06:00
Author
Owner
Copy Link

@vbose1 commented on GitHub (Sep 14, 2018):

Find the solution repository was created by default in Owner team. My team was different.

@vbose1 commented on GitHub (Sep 14, 2018): Find the solution repository was created by default in Owner team. My team was different.
GiteaMirror commented 2025-11-02 04:33:05 -06:00
Author
Owner
Copy Link

@vbose1 commented on GitHub (Sep 14, 2018):

@lafriks Can I delete Owner team?

@vbose1 commented on GitHub (Sep 14, 2018): @lafriks Can I delete Owner team?
GiteaMirror commented 2025-11-02 04:33:05 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Sep 14, 2018):

Owner team can not be deleted. You can add repository to multiple teams. In Team settings click link 0 repositories and add repository to that team.

@lafriks commented on GitHub (Sep 14, 2018): Owner team can not be deleted. You can add repository to multiple teams. In Team settings click link `0 repositories` and add repository to that team.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2332
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?