| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
The smart-http interface starts http-backend which calls receive-pack.
Unfortunately we were performing the dangling-HEAD check
after calling receive-pack ourselves,
so when using smart-http we weren't performing the check.
By moving this into the post-receive hook
the check can be performed in smart-http too.
|
| | |
|
| |
|
|
|
| |
HOME is needed to find the modified git config.
It not being set before now was an oversight.
|
| | |
|
| |
|
|
|
|
|
|
| |
Because additional git config is now required to use ext:: urls
running git directly is not sufficient
as the HOME variable needs to be set to locate the modified config.
It's simplest to modify the yarns to use $GTT rungit to do this.
|
| |
|
|
|
|
|
|
| |
Newer versions of git block the ext:: protocol by default,
so that a repository with submodules may not run arbitrary code.
Whitelisting the ext:: protocol for the test users is the minimum effort
required to make it work again.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
In order to make this work, I had to rework password handling in the test
suite, and also redo the http unwrapper to use wget instead of executing the
cgi directly. All yarn IMPLEMENTs which use $GTT runcommand and don't pass the
stdin, *MUST* explicitly use </dev/null to prevent hangs in http mode.
|
| | |
|
| |
|
|
|
|
| |
When deleting or renaming users, the htpasswd file needs
updating so that we don't leave stale or incorrectly assigned
user credentials around.
|
| |
|
|
|
| |
In order to support the sysbranch work I'm doing for the CI, we need
LUA_INIT to get passed through in the environment.
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| | |
Basic hook tests which verify preauth commandline and post receive hooks.
|
| | |
| |
| |
| |
| |
| | |
This adds POST_RECEIVE properly as a hook. We move the current behaviour into
hook functions, separating out core updates from the Supple hook run, to permit
plugins to interpose behaviour.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This hook is permitted to adjust the command line before it is
passed on to command authorisation. This is needed for a number
of use-cases requested around permitting a plugin to provide domain
specific command line shapes without needing to adjust Gitano's
core command structures.
|
| | |
| |
| |
| |
| |
| |
| | |
This adjusts the core gitano module to export gitano.hooks.
In addition, we bump the API version to 1.1.0 since we're adding
in a new API (hooks)
|
| | |
| |
| |
| |
| |
| | |
This adds hook names to the gitano.hooks API which is there to
explain what the hook functions should do, and to provide a logical
name for hooks, rather than expecting people to not typo strings.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The gitano.hooks module is intended to support a variety of hooks, both those
defined by Gitano itself; and those added by plugins.
Hooks are meant as a means to propagate information and also to permit
alteration of arguments before work is done.
|
| | |
| |
| |
| |
| | |
This adds support for gitano-test-tool to set environment variables. We also
add some yarn implementations for doing this.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Having both local definitions for each exported pattern
and the export in the package was not helpful,
and in fact caused accidents while developing
where the package was filled with undefined variables.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Gitano's executables, in addition to being required for operation,
are intended to be examples of how to use the gitano library,
so rather than importing with require "gitano.patterns",
gitano should be imported and use gitano.patterns.
No changes to imports are made inside lib/gitano/
because this would cause an import loop.
|
| |/
|
|
|
|
|
| |
This has moved every pattern that wasn't obviously just for string manipulation
and has in the process of doing so reworked some logic
so that fewer distinct patterns are used,
and the repository path normalisation has been unified.
|
| | |
|
| |\
| |
| |
| | |
(slight tweaks as per review)
|
| | | |
|
| |/ |
|
| |\ |
|
| | |
| |
| |
| |
| | |
This change ensures that the server-info files are created
at the point that a repository is realised.
|
| | |
| |
| |
| | |
Even new repositories need http server info files.
|
| |\ \ |
|
| | | | |
|
| | |/
| |
| |
| |
| | |
Ensure that when we loop through the answer files, we actually
read all of them, not just the first.
|
| |\ \ |
|
| | | | |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| | |
The gitano-test-tool coverage was consuming a lot of time and slowing down
coverage test running. In addition it was around 2/3 of all processes covered
and as such was making coverage report generation slow too.
This change adds a COVER_GTT makefile argument which must be set to 'yes' in
order for COVERAGE=yes test runs to also cover gtt.
|
| |\ \
| |/
|/| |
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
