Force Git push on SourceForge

I’m trying to rollback a Git repository on SourceForge. I tried the following:

git reset --hard 9ac2e31ca4a155d4c36780b4329626045a7f40ed
HEAD ist jetzt bei 9ac2e31 Fix warnings

git push -f origin master
Total 0 (delta 0), reused 0 (delta 0)
remote: error: denying non-fast-forward refs/heads/master (you should pull first)
To ssh://
 ! [remote rejected] master -> master (non-fast-forward)
error: Fehler beim Versenden einiger Referenzen nach 'ssh://'

How can I override the master branch for a remote SourceForge Git repository?

  • Changed username to push with to atlassian stash - update-server-info?
  • How do I rebase a chain of local git branches?
  • How do I clone a git repository to a new project?
  • How to solve git merge error “Swap file .MERGE_MSG.swp already exists”
  • How do I clone a job in jenkins?
  • Git: Understanding post-receive
  • Can I use git-svn to clone a specific branch of a remote SVN repo and commit back to it?
  • Resolving conflicts with egit. No “Team -> Add” option
  • Best way for git two-way synchronization
  • After merging, but before committing, how can I force a manual re-merge on a specific file?
  • `gitk` program found using the `where` command but cannot be executed?
  • Git Subtree merge strategy - how does the setup itself carry over across cloning?
  • 2 Solutions collect form web for “Force Git push on SourceForge”

    Since denyNonFastforwards is a server-side config, you need to access to your repo on the SourceForge side somehow.

    As your ticket mentions, this is done with an interactive shell service, but that supposes you can use ssh to open a secure shell.

    Running “sf-help --scm” in the shell will show you your repo paths.
    Just tweak the denyNonFastforwards = true to false for a bit, do your push, and then set it back to true (for safety).

    However, a message like “ssh: connect to host port 22: Connection refused” could mean that:

    • It could be blocked on the client side (check if you can ssh to other services, like GitHub, even though it won’t be an interactive session)
    • or it could be the result of an outage on SourceForge side (but their status page doesn’t report any recent incident)

    Double-check the SourceForge SSH documentation.

    Here are detailed instructions to connect to your Sourceforge account and change the config file and enable non-fast-forward updates.

    You can change denyNonFastForwards of a standard Sourceforge project from your computer with the following commands :

    • Connect to your SSH account using Interactive Shell with command ssh -t create. Notice that the URL is different from the one of your project:
    $ ssh -t create
    The authenticity of host ' (ip)' can't be established.
    ECDSA key fingerprint is SHA256:key
    Are you sure you want to continue connecting (yes/no)? yes
    Warning: Permanently added ',ip' (ECDSA) to the list of known hosts.
    Requesting a new shell for "user" and waiting for it to start.
    queued... creating... starting...
    This is an interactive shell created for user user,users
    Use the "timeleft" command to see how much time remains before shutdown.
    Use the "shutdown" command to destroy the shell before the time limit.
    For path information and login help, type "sf-help".
    • Find the file config using sf-help --scm or pwd, it should be located in folder /home/git/p/myproject/code.git/.

    • Read the config file to check denyNonFastforwards status, it is indeed set to true:

    [user@shell-22003 code.git]$ cat config
            repositoryformatversion = 0
            filemode = true
            bare = true
            sharedrepository = 2
            denyNonFastforwards = true
    • Start vi to modify the file, change true to false:
    [user@shell-22003 code.git]$ vi config
            repositoryformatversion = 0
            filemode = true
            bare = true
            sharedrepository = 2
            denyNonFastforwards = false
                                1,1           All
    • Type :w to save the change and :q to exit vi.

    The error denying non-fast-forward should not appear anymore.

    Git Baby is a git and github fan, let's start git clone.