rugged

An error occurred while installing rugged

≯℡__Kan透↙ 提交于 2019-12-03 06:28:41
问题 Following this tutorial [link] to install gitlab on a dedicated server. I need to : sudo -u git -H bundle install --deployment --without development test postgres aws But an error occurred while installing rugged : Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension. /usr/local/bin/ruby extconf.rb checking for cmake... no ERROR: CMake is required to build Rugged. *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary

An error occurred while installing rugged

馋奶兔 提交于 2019-12-02 20:00:58
Following this tutorial [ link ] to install gitlab on a dedicated server. I need to : sudo -u git -H bundle install --deployment --without development test postgres aws But an error occurred while installing rugged : Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension. /usr/local/bin/ruby extconf.rb checking for cmake... no ERROR: CMake is required to build Rugged. *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options.

Do GitHub and GitLab support git clone's --filter parameter?

家住魔仙堡 提交于 2019-12-01 21:52:24
I want to use git's partialClone feature. In this answer I saw the git clone --filter=tree:none <repo> command. But when trying to execute on github, the prompt warning: filtering not recognized by server, ignoring . It did not work. I want to know if it is not supported by the GitHub website, or if there is a problem with my settings. I asked the feedback staff of GitHub and have not got the answer from the technician. This almost certainly isn't supported by GitHub or GitLab yet. The --filter option is under active development and isn't really ready for general-purpose consumption yet.

Performing a “fast-forward” merge with Rugged

生来就可爱ヽ(ⅴ<●) 提交于 2019-12-01 09:36:59
Using Rugged, what's the canonical way to perform a fast-forward "merge"? From here I found one possible lead: # Move branch forward # Since there's no fast-forward merge in this lib yet, do it by hand. br = repo.branch "master" br.move 'master-old', true if br != nil repo.create_branch 'master', commit_sha #br.delete! # No real harm in this hanging around But I'm curious if there's room for improvement here. There is no need for an operation called "fast-forward merge" libgit2 since a so-called ff-merge is updating the current branch to whatever commit is on the other branch, which does exist

Performing a “fast-forward” merge with Rugged

寵の児 提交于 2019-12-01 08:56:23
问题 Using Rugged, what's the canonical way to perform a fast-forward "merge"? From here I found one possible lead: # Move branch forward # Since there's no fast-forward merge in this lib yet, do it by hand. br = repo.branch "master" br.move 'master-old', true if br != nil repo.create_branch 'master', commit_sha #br.delete! # No real harm in this hanging around But I'm curious if there's room for improvement here. 回答1: There is no need for an operation called "fast-forward merge" libgit2 since a