View Code? Open in Web Editor
NEW
Twgit is a free and open source assisting tools for managing features, hotfixes and releases on Git repositories. It provides simple, high-level commands to adopt the branching model describes in our documentation. Supported OS: Debian/Ubuntu Linux, Mac OS X 10.8 (Mountain Lion) or lower.
Home Page: http://twgit.twenga.com/
License: Other
PHP 55.17%
Shell 44.49%
Makefile 0.34%
twgit's People
twgit's Issues
that display:
– the full name of the feature if connector Redmine or Github setted
– same indications as thoses displayed at the end of "twgit feature start":
Already on 'feature-4568'
(i) Local branch 'feature-4568' up-to-date with remote 'origin/feature-4568'.
/!\ Tags not merged into this branch: at least '1.1.2' to 'v1.3.0'. If need be: git merge --no-ff v1.3.0
in a similar way to twgit feature merge-into-release...
Use wiki section of github.
ie : clean, update, init, ...
getRedmineSubject() and displayRedmineSubject() need decoupling.
7bb46db [twgit] Init feature 'feature-xyz'.
6b1a6b7 [twgit] Init feature 'feature-xyz'.
Same as twgit feature merge-into-release, but in a loop, trying to find the largest merge of features without conflicts.
Subhelp correctly finish with a 0 error code.
Perhaps with options_handler::require_parameter() returning an error code...
Getting started, help on command prompt, ...
Concern get_all_tags() function.
Title of Redmine tickets are already fetched while feature listing. But not yet title of project or sub-project.
Add a first unit test using Travis-ci.org
– duplicate tag 1.2.1
– merge-into-release 3410 instead 4210
=> /!\ Tag 'vx.y.z' already exists!
$ git checkout v1.1.0
warning: refname 'v1.1.0' is ambiguous.
Switched to branch 'v1.1.0'
$ twgit feature start 34701
Check valid ref name...
Check clean working tree...
git# git fetch --prune origin
Check local branches...
Check remote features...
Get last tag...
Last tag: v1.1.1
git# git checkout -b feature-34701 v1.1.1
warning: refname 'v1.1.1' is ambiguous.
warning: refname 'v1.1.1' is ambiguous.
fatal: Ambiguous object name: 'v1.1.1'.
/!\ Could not check out tag 'v1.1.1'!
Make git checkout stable.
Clean makefile
...
Start a new feature F1 (from last tag) and merge F2 into F1: twgit feature start F1 F2
If release name is not X.Y.Z, then twgit release remove fail.
Periodically archive .history.error and .history.log
Missing description, requirements, installation and a pointer to the documentation.
Useful to redefine TWGIT_BASH_EXEC or TWGIT_UPDATE_AUTO, ...
Shows features merged into the release when the tag was created.
twgit list [<tagname>] [-F]
List 5 last tags with included features. Add -F to do not make fetch.
If is specified, then focus on this tag.
Because that lead to a lot of "warning: refname 'v1.1.1' is ambiguous."...
=> exec_git_command "git checkout --track ...
And not just yes/no for the last tag...
Add twgit init command to initialize empty repositories (as git init):
create stable branch
create first tag
...
autoupdate() currently observe master branch...
Contextual help for other commands also need precision on added prefixes.
Bad twgit version displayed in about section. Missing change directory before "git describe".
Add command callable by a cron to send mail to main committers of old features (number of tags no merged into).
– Display news of CHANGELOG
– Inform of Bash autocompletion update
– Describe concrete evolution of config file
and choose between camelCase notation or delimiter-separated words ('_').