Closed cordoval closed 9 years ago
A utility for cloning and fetching your remote git repositories from GitHub.
A dashboard of Github Pull Requests https://prs.paas.allizom.org/gushphp/gush
@cordoval Maybe make this a wiki page so it's community editable.
that tool you just posted is like dbu/dashboard you have not posted that yet here :baby:
the problem with wikis is it will not update us and also it will not be well moderated.
@leoj3n could you please point which ones have you tested yourself? it would be a good idea to filter which ones can provide the rapid flow that we want for team development and contribution.
I have probably less than half of these installed, but I do mean to try them all when I have a chance... I am busy with more important (to me) things this month. But I do think it would be huge to go through these and document the similarities and differences, and goals of each.
I'd say git-flow is the most similar to Gush of the ones I've tried.
:baby: what are your own thoughts on Gush, are you using it?
I only played with Gush once, as a test: https://gist.github.com/leoj3n/8434445
Currently I am not working on a large project that needs any kind of meaningful git history. I plan on eventually building a company/product, and will certainly use Gush, in addition to whatever other tools I can work into the mix. In more of a research/collection/organize phase right now.
I can move this list to a repo of my own if it's cluttering this topic with unrelated information, just lmk.
@leoj3n as someone interested in correcting you respectfully, let me clarify some points:
. Gush is not only for large projects, i use daily Gush to develop solo, it keeps working with PRs to review my own diffs rather than relying on committing review my own changes, it is less keystrokes and automation, helps with units of thought
. Gush is not only about history but about versioning and helping maintaining the package
. Your review of Gush is too early, almost prehistoric, you have no idea how Gush has changed, you will be surprised totally
. Again Gush is for everyday doing, it will save you tons of hours as a solo and many more hours if in team for everybody
About the information here, please keep it coming in comments, I like to have a complete reference so we can beat everybody else :baby:
you rock, I hope I shake your notions on Gush and on your own needs :dancer:
@cordoval Thanks for the detailed thoughts; I will get myself up to date with the latest Gush.
i bet maybe none of these tools support multirepos like Gush does @leoj3n ?
Multirepo support? Don't see anything about that in the Gush documentation.
On 26 Apr 2014, at 1:33, Luis Cordova wrote:
i bet maybe none of these tools support multirepos like Gush does @leoj3n ?
Reply to this email directly or view it on GitHub: https://github.com/gushphp/gush/issues/18#issuecomment-41461464
time for you to contribute to the docs :baby: add yourself to the composer.json on your PR
@leoj3n just run gush core:configure
and you will see it all
There are some explanations prompted by a question from @flip111 on this ticket https://github.com/symfony/symfony/issues/10864 that would be good to analyze if Gush does not already meet those requirements
https://github.com/aanand/git-up thanks @nVitius
https://github.com/cargomedia/github-issues/issues/34 extract anything that needs or is worth extraction there.
Maybe they can also be invited to use gush if they are not already :blush:
@sstok interesting thing on git-up is like the command gush b:s, this latter only updates the current branch, one branch only, i usually do this sometimes when i see after a PR merge i am shifted. Other than that git-up is not really that great, it uses git configuration under .git/config or globally under ~/.gitconfig, but really this makes it non portable with the project across a team or FOSS or shared environment. We are in a good direction by using a .gush.yml local and global and also keep separate git and gush because git will change for sure. Any thoughts on making gush b:s more powerful? or is simple and good. I like simplicity, the only thing we can improve probably is to do less typing for very common tasks. And I can't think of any right now regarding an update since gush b:s covers things well.
Gibo is interesting tool to access .gitignore templates but not sure really if this is a common thing to do so no further comment really.
Often i am seeing my branches not being removed automatically after someone else merge a PR i sent to a repo. This can create a lot of junk on github. I say we implement something like this but for gush cc @sstok ? Yes/No so we can create a ticket for this. Also I never remember the command to clear all local branches. git-sweep is more for remote branches already merged, but i never recall how to do it locally. Which should be a command also
i will create a git-sweep like ticket and then close this issue finally. We will still follow up on the improvements on other tools but so far is good.
ref https://github.com/cordoval/gush/issues/27
Git and GitHub tools
[gushphp/gush][]