gitolite

How to keep/maintain public and private code in the same repository? (at repository hostings)

吃可爱长大的小学妹 提交于 2019-12-05 02:28:12
问题 I'm working on my own project which has two parts: A. kernel/generic code (public part) B. code which works with proprietary protocol etc (private part, available for me and a few authorized persons) I want repository hosting (maybe github, assembla, ...) which allows working in public and private branches in the same repository. I don't want two repositories because I'm actively working on both parts and I want to avoid diverged repositories. Which solution is available for me? 回答1: which

GitSmartHTTP for gitolite repositories over Apache does not allow me to push

本秂侑毒 提交于 2019-12-05 01:36:52
I am setting up a git-http-backend CGI script to handle my git.domain subdomain. The server is behind an ELB (elastic load balancer) on AWS cloud. My server config is as follows (my git hosting is handled by gitolite): <VirtualHost *:80> ServerName git.domain ServerAdmin hjpotter92+git@domain #SuexecUserGroup git git DocumentRoot /opt/gitolite/repositories/ PerlLoadModule Apache::Authn::Redmine SetEnv GIT_PROJECT_ROOT /opt/gitolite/repositories/ SetEnv REMOTE_USER=$REDIRECT_REMOTE_USER # Have also tried removing this variable SetEnv GIT_HTTP_EXPORT_ALL ScriptAliasMatch \ "(?x)^/(.*/(HEAD | \

Git/gitolite: moving repos after setting up gitolite

空扰寡人 提交于 2019-12-04 22:04:19
问题 I am in the final phases of getting Git and Gitolite working. This is the current situation: 回答1: The repositories under Gitolite management don't have working copies. So what you have to do is create another repositories with working copies, commit the data and push them to the gitolite-managed ones. The easiest thing is to do that on the server directly. Therefore under each of the www directories, do: cd /home/X/www git init git remote add origin /home/gitolite/repositories/X.git git add .

How to install hooks in gitolite

六眼飞鱼酱① 提交于 2019-12-04 19:11:31
问题 I've read all the documentation about hooks, similar questions and a lot of code but I can't track where is the error in my procedure. I need to install a simple hook in my gitolite installation (made with an rpm package on CentOS) so here is what I did: To install gitolite (some time ago): Installed the rpm package # su - gitolite $ gl-setup /tmp/fabio.pub (as gitolite user) Now to install the hook: Created a sample file post-update with the hook code in ~gitolite/.gitolite/hooks/common and

please help me understand gitolite users [closed]

只谈情不闲聊 提交于 2019-12-04 17:38:09
For some reason my gitolite didn't come with a sample config file and i can't seem to find one anywhere, im sure this question is answered in that file if someone can find me a copy, please!! Anyways, the format of the gitolite config file is simple enough, here's a snip from mine gitolite conf # please see doc/gitolite.conf.mkd for details on syntax and features @nmscDevs = dev1@compaid.com dev2@compaid.com dev3@compaid.com @buildMgr = william_slepecki@compaid.com dev4@compaid.com repo gitolite-admin RW+ = gitadmin william_slepecki@compaid.com repo grindstone RW+ = gitadmin RW+ prod$ =

git push origin DENIED by fallthru, hook declined: gitolite

感情迁移 提交于 2019-12-04 16:45:52
问题 I am having a problem pushing with git using Gitolite. When I try this: git push origin :refs/tags/deployment I get this error: remote: D NAME/install.py repos michael DENIED by fallthru remote: error: hook declined to update refs/tags/deployment To gitolite@admin:repos ! [remote rejected] deployment (hook declined) error: failed to push some refs to 'gitolite@admin:repos' I have given the group deploy [of which the user michael is a member of] permission to delete branches in the Gitolite

Block and/or Identify Fake author name/email in GIT

喜你入骨 提交于 2019-12-04 15:12:52
问题 I want to block fake users in git commit . That means one user must not be able to change his/her email with someone else. I use gitolite. How can I implement this feature? As I have users' public keys, can I bind their email/name to that public key? 回答1: As I have users' public key, can I bind email/name with that public key? Not natively: Gitolite only works with the user id (as extracted from the http or ssh session and set in a variable GL_USER ) So you need to have that information

Git hook to detect file changes that contain a certain string

ぐ巨炮叔叔 提交于 2019-12-04 14:32:12
I want to warn a user if their code includes a certain string and alert people via email. Right now I'm using a post-receive hook because the detection needs to be done on the server side. I am updating a server-side repository and running something like git diff-tree -r --name-only --no-commit-id $2 | xargs grep foo to detect bad string "foo." Problems with this approach: I don't like maintaining and entire working version of the repository server-side It scans the entire file, not just the changes. edit I solved this problem replacing the above with: git show $2 | grep ^+ ... Is there a

git ignore filemode config isn't working

拥有回忆 提交于 2019-12-04 14:01:58
I am using gitolite git server on a ubuntu linux server. I used a hook that will be called on every push and will update a server's directory(which include live site's source code). Now, whenever I change something on my local pc and push the changes to server, the hook is being called and the pull request are being executed fine. But, problem is, the files which were updated, are now having changed permission. Like: rwxrwxr_x (before) rwx_____x (After) After few searches, I did came up with this solution . I did tried it with both my global git config and repository specific config settings.

Is it possible to implement repo based hooks in Gitolite?

喜夏-厌秋 提交于 2019-12-04 13:45:37
I want to implements repo based hooks in gitolite. Is it Possible ? I am using gitolite 3 (g3). Since Gitolite 3.6+, it is possible with " repo-specific hooks ": add this line in the rc file, within the %RC block, if it's not already present, or uncomment it if it's already present and commented out: LOCAL_CODE => "$rc{GL_ADMIN_BASE}/local", uncomment the ' repo-specific-hooks ' line in the rc file or add it to the ENABLE list if it doesn't exist. If your rc file does not have an ENABLE list, you need to add this to the POST_COMPILE and the POST_CREATE lists. Click here for more on all this.