github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-11 09:40:19 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

can't push local repo to remote #4532

New Issue
Closed
opened 2025-11-02 05:53:37 -06:00 by GiteaMirror · 8 comments
GiteaMirror commented 2025-11-02 05:53:37 -06:00
Owner
Copy Link

Originally created by @iwzoo on GitHub (Dec 22, 2019).

  • Gitea version (or commit ref):
    1.11.0+dev-352-g66028d58f built with GNU Make 4.2.1, go1.13.4 : bindata, sqlite, sqlite_unlock_notify
  • Git version: 2.22.0
  • Operating system: Debian, Docker
  • 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

  1. Create new repo in Gitea
  2. Create local repo, and run
git init
touch readme.md
git add readme.md
git commit -m "initial commit"
git remote add origin repo_url
git push -u origin master
  1. remote repo keeps empty. nothing pushed.
    ...

Screenshots

Originally created by @iwzoo on GitHub (Dec 22, 2019). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) 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): 1.11.0+dev-352-g66028d58f built with GNU Make 4.2.1, go1.13.4 : bindata, sqlite, sqlite_unlock_notify - Git version: 2.22.0 - Operating system: Debian, Docker - 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 1. Create new repo in Gitea 2. Create local repo, and run ``` git init touch readme.md git add readme.md git commit -m "initial commit" git remote add origin repo_url git push -u origin master ``` 3. remote repo keeps empty. nothing pushed. ... ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the issue/staleissue/needs-feedback labels 2025-11-02 05:53:37 -06:00
GiteaMirror commented 2025-11-02 05:53:37 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Dec 22, 2019):

We need some more information I'm afraid.

What version of Gitea?

Do you get any logs in Gitea when you push?

It looks like you're pushing over http is that correct?

Are your Gitea repositories mounted on an executable partition? If they are mounted noexec or user then I'm afraid that won't work as Gitea is informed by git hooks about pushes.

@zeripath commented on GitHub (Dec 22, 2019): We need some more information I'm afraid. What version of Gitea? Do you get any logs in Gitea when you push? It looks like you're pushing over http is that correct? Are your Gitea repositories mounted on an executable partition? If they are mounted noexec or user then I'm afraid that won't work as Gitea is informed by git hooks about pushes.
GiteaMirror commented 2025-11-02 05:53:38 -06:00
Author
Owner
Copy Link

@iwzoo commented on GitHub (Dec 24, 2019):

We need some more information I'm afraid.

What version of Gitea?

Do you get any logs in Gitea when you push?

It looks like you're pushing over http is that correct?

Are your Gitea repositories mounted on an executable partition? If they are mounted noexec or user then I'm afraid that won't work as Gitea is informed by git hooks about pushes.

Gitea: 1.11.0+dev-352-g66028d58f built with GNU Make 4.2.1, go1.13.4 : bindata, sqlite, sqlite_unlock_notify

Yes, I'm using http for pushing.

Do you mean the the mount of /data should be executable (without nonexec option)?

@iwzoo commented on GitHub (Dec 24, 2019): > We need some more information I'm afraid. > > What version of Gitea? > > Do you get any logs in Gitea when you push? > > It looks like you're pushing over http is that correct? > > Are your Gitea repositories mounted on an executable partition? If they are mounted noexec or user then I'm afraid that won't work as Gitea is informed by git hooks about pushes. Gitea: 1.11.0+dev-352-g66028d58f built with GNU Make 4.2.1, go1.13.4 : bindata, sqlite, sqlite_unlock_notify Yes, I'm using http for pushing. Do you mean the the mount of /data should be executable (without nonexec option)?
GiteaMirror commented 2025-11-02 05:53:38 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Dec 24, 2019):

Yes, exactly that.

@zeripath commented on GitHub (Dec 24, 2019): Yes, exactly that.
GiteaMirror commented 2025-11-02 05:53:38 -06:00
Author
Owner
Copy Link

@iwzoo commented on GitHub (Dec 24, 2019):

is there any chance or plan to make it working on noexec partition?

@iwzoo commented on GitHub (Dec 24, 2019): is there any chance or plan to make it working on noexec partition?
GiteaMirror commented 2025-11-02 05:53:38 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Dec 26, 2019):

@iwzoo I think it can't. Hooks scripts need execute permission.

@lunny commented on GitHub (Dec 26, 2019): @iwzoo I think it can't. Hooks scripts need execute permission.
GiteaMirror commented 2025-11-02 05:53:38 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Dec 26, 2019):

So there is actuallly a potential technique with setting the GIT_HOOK_DIR environment variable. However I just don't have time to do it as yet and it's potentially a little fiddly as we would have to deal with other hooks etc.

@zeripath commented on GitHub (Dec 26, 2019): So there is actuallly a potential technique with setting the GIT_HOOK_DIR environment variable. However I just don't have time to do it as yet and it's potentially a little fiddly as we would have to deal with other hooks etc.
GiteaMirror commented 2025-11-02 05:53:38 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Feb 24, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 24, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.
GiteaMirror commented 2025-11-02 05:53:38 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 9, 2020):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Mar 9, 2020): This issue has been automatically closed because of inactivity. You can re-open it if needed.
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 issue/needs-feedback issue/stale
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#4532
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?