| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
The previous version fails to handle nested branch names containing
slashes. For example, if pushing a single new branch named
`feat/example`, the script would set HEAD to `feat` and remain dangling.
Signed-off-by: Malfurious <m@lfurio.us>
|
|
Since it is now allowed to remove the remote default branch, this script
needs to handle cases where there are no branches following a push.
In this case, the `git symbolic-ref` command will fail, and we return
our standard warning for when HEAD is dangling.
Signed-off-by: Malfurious <m@lfurio.us>
|
|
The repository is being reworked to decouple its roles as normalmode
source and gitolite-admin config. The gitolite-admin repository will be
entirely separate. So there is no need to keep the conf or local
directories around where they are at.
Signed-off-by: Malfurious <m@lfurio.us>
|
|
By default, the idle times shown by cgit only reflect the most recent
push to the master branch - and that is the time of the push, not of the
actual commit.
This patch causes the age/timestamp to be set by pushes to any branch.
The times will reflect the age of the youngest commit on any branch or
tag.
Signed-off-by: Malfurious <m@lfurio.us>
|
|
The non-core feature 'symbolic-ref' that ships with gitolite opens a
bigger hole than I would intend to (in the form of allowing arbitrary
git-symbolic-ref commands to be executed).
As an alternative, a post-git gitolite trigger is added. Its only
purpose at the moment is to check on the state of HEAD following any
pushes.
Under normal circumstances, HEAD will point to a valid branch, or on a
first push, the master branch will be provided, validating HEAD. If
after the first push, there is no branch called master, we assume the
creator wishes to use another name for the default branch, and so will
update the ref if doing so is unambiguous (there is only one other
branch). If multiple non-master branches are present in this case, a
warning is issued, and HEAD is left invalid, awaiting a later push to
master.
This _should_ only be an issue for the first push. Once HEAD refers to
a valid branch (of any name), this action is bypassed going forward.
Signed-off-by: Malfurious <m@lfurio.us>
|
