This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
commit ad9a4c9009662f459e8a0dded614cd20ec28d6b2
tree b176b8b7224e09c10b3a653c663a1454f1fcb567
parent 8bdda36750dde49dd6f8e47eaa20b51c0c1989ef
tree b176b8b7224e09c10b3a653c663a1454f1fcb567
parent 8bdda36750dde49dd6f8e47eaa20b51c0c1989ef
| name | age | message | |
|---|---|---|---|
| |
README.rdoc | ||
| |
Rakefile | ||
| |
app/ | ||
| |
db/ | ||
| |
gems/ | ||
| |
init.rb | ||
| |
install.rb | ||
| |
lib/ | ||
| |
tasks/ | ||
| |
test/ | ||
| |
tmtags | ||
| |
todo.taskpaper | ||
| |
uninstall.rb |
README.rdoc
Mingle Git Plugin
A quick spike on getting a git plugin for mingle working. This should not be considered production ready - so use with caution!
Features
The git plugin currently supports:
* Pulling in messages from git commits to the master branch. * Automatically pulls commits from the remote origin's master branch. * Showing a list of files that were added/deleted/modified. * Associating commits with the corresponding Mingle user.
Instructions
0. Copy this plugin to your mingle install path/vendor/plugins 1. Login as the user running the Mingle Server (unix login). 2. Clone the project's git repository. 3. Enter the path you cloned to in the project repository settings section. 4. (Optional) Enter the git email addresses as the "Subversion user" in the users admin. 5. (Optional) If you want the "Source" link to redirect to github, modify config/routes.rb by changing :controller to "git_source" instead of "source", and make sure you put in the github URL when configuring the project repository settings.
Known limitations
* Potential problems with mingle revision numbers assumed to be sequential. Mingle caches the revision history, and if check-ins occur in git that change the order, the cache would not be correct.








