You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Updates the repo with changes from remote master# Warning: This resets the repo before pulling in the changes.#defupdate# Reset --hard repo before updatereset!if@settings[:reset_before_update]# Fetch changes from originrepo.fetch('origin',credentials: credentials)# Create the merged index in memorymerge_index=repo.merge_commits(local_branch,remote_branch)# Complete the merge by comitting itRugged::Commit.create(repo,parents: [local_branch,remote_branch],tree: merge_index.write_tree(repo),update_ref: update_ref,message: update_message,author: commit_author,committer: commit_author)reload!end
According to some StackOverflow comments, repo.merge_commits(local_branch, remote_branch) does not merge the remote changes into the checked out working tree. Instead one has to checkout the changes after the merge.
however when I do something with the repositories in redmine then the public key is automatically replaced with the path to the key again which then breaks the ssh as well.
That could be related, as Mr. gitolite-rugged does not only delete nice message files, but also public keys and other more substantial changes to the gitolite-admin repo.
redmine_git_hosting seems to be incompatible with remote changes to the gitolite-admin repository.
On my dev machine, I add a new file to the gitolite-admin repository, commit and push it
Now, I go to Redmine and add a Gitolite repository to an existing project
Afterwards, I get the feeling that somebody deleted my last commit to the gitolite-admin master. So I will go and check
I assume, that the update method of GitoliteAdmin from the gitolite-rugged repository should be responsible for merging my changes, but deletes them instead.
https://github.com/jbox-web/gitolite-rugged/blob/devel/lib/gitolite/gitolite_admin/accessors.rb#L93
According to some StackOverflow comments, repo.merge_commits(local_branch, remote_branch) does not merge the remote changes into the checked out working tree. Instead one has to checkout the changes after the merge.
http://stackoverflow.com/questions/27971814/rugged-merge-commit-from-origin-does-not-update-working-tree
http://stackoverflow.com/questions/21842783/rugged-fetch-pull-rebase-possible#27290470
The text was updated successfully, but these errors were encountered: