quilicicf / gut Goto Github PK
View Code? Open in Web Editor NEWEin Gut git Fluss
License: Apache License 2.0
Ein Gut git Fluss
License: Apache License 2.0
I'd like to know which branches are stale (remote branch merged and deleted) so I can clean up my local repository.
N/A
The listing should add the information in front of each line (with a color code).
Bonus: allow to select the branches for deletion or to delete stale branches from
gut obliterate
(see which makes more sense)
gut burgeon
tries to create branch master.
No applicable yet
It should fail miserably
Run
gut burgeon
Some parameters to CI jobs can't be guessed. Let's have Gut prompt the users for those.
Not applicable yet
When configuring a CI job, it should be possible to ask the user for one of the parameter's value.
Example:
{
"ci": {
"jenkins": {
"build": {
"server": "personal",
"uri": "/jobs/gut",
"body": {
"branch_or_tag": "$currentBranch",
"myParameter": "$ask(myParameterName)"
}
}
}
}
}
When running gut ci
, Gut should prompt the user for the value of myParameterName
.
It should be simple to checkout master, the version branch, the feature branch and the base branch.
Not applicable yet
The command switch
should accept the parameters:
Gut is currently not tested, let's fix that.
Not applicable yet
Not applicable yet
There should be a command to copy the current branch into the system's clipboard.
Not applicable
You can use the package copy-paste.
The README is quite empty right now. It should give a glimpse of what Gut does.
Not applicable yet
🚨 You need to enable Continuous Integration on all branches of this repository. 🚨
To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.
Since we didn’t receive a CI status on the greenkeeper/initial
branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.
If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/
.
Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial
branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.
Using gut switch -r 'whatever'
doesn't find branches that only exist on the remote.
Not applicable yet
The remote branches should be shown in the choices too!
Run gut switch -r <regex>
where regex matches a branch that only exists on the remote.
Some repos don't have associated projects in bug trackers (micro-services for example). This means the commit templates may contain different project ids.
Gut should allow users to configure the template so that the project is prompted when committing.
Not applicable yet
Maybe add a syntax like this: "commitMessageTemplate": " (${prompt:projectId}-$ticketNumber)"
Gut would then prompt the user for the projectId
when committing.
Use gut execute
Currently, when cd-ing to repository flukteplukte
, one might have to type *ukte
for the search to match. This is a shame as *
is more complex to type on lots of keyboard layouts than letters.
Not applicable yet
I'd expect ukte
to match my repository as I'm quite sure no other will match this.
Auto-surrounding the search by *
would make the search wider and simplify typing in most cases. It'll have the drawback of sometimes matching too much (ex: gut
now matches Gut-test
) but most of the time the pros outweigh the cons.
Running gut replicate --help
does not show the arguments to the method.
Not applicable yet
A documentation like all other commands get.
Run gut replicate --help
It is way easier to type a command when there's tab completion. Currently, no tab completion has been implemented, meaning Gut is behind Git on this point.
Not applicable yet
There should be tab completion for every parameter to every command in Gut.
You can split this in multiple PRs of course, for example one PR for git items completion and one for yargs parameters completion (based on parameter's choices).
I've got no preferences for the dependencies to use for tab completion but you should probably check this link.
The command audit
should display the number of files that were changed.
Not applicable yet
Currently, trying to create a PR on a branch that was never pushed fails miserably.
Let's remove one useless command!
Add the version of Gut you're using
The branch should be pushed before creating a PR.
The push should be non-blocking (don't wait until it's finished to configure the PR).
The push should only occur if the branch was never pushed before or if the local branch is above the remote branch.
cd "$aRepo"
gut burgeon -d myBranch
echo toto > tata
gut pile
gut execute -m A message
gut pr
Add slack integration to query-review feature.
Not applicable yet
The query-review feature should ask the user if he wants to post a message on a chat (only Slack supported to begin with).
You can see how it's done in the current bash implementation here
$gut install
fails because of duplicate variable declaration
The review tool is currently extracted from the repository path but in the repository path, it is the git server that is present, not the review tool.
Not applicable yet
The review tool should be extracted from repository config's reviewTool
attribute.
The command gut execute -m 'message'
fails when there is no message template in the repository's configuration file.
Not applicable yet
The the commit be done without suffix.
Run gut execute -m 'message'
in a repository:
The command gut pr
doesn't work when the branch has never been pushed.
Not applicable yet
The branch should be automatically pushed if it was never pushed before.
In any repository, run:
gut switch -m
gut burgeon -n 82 -d prShouldPushFirst
# commit anything, otherwise gut will notice nothing was updated from base branch and won't try to create the PR
gut pr
The vulnerabilities added by the dependency don't look like they're going away: Kong/unirest-nodejs#113
It should be easy to jump to a repository inside the repository folder.
Not applicable yet
The repository should be searchable:
jump Gut
jump Gu
jump -g github -o quilicicf Gu
jump -g githu -o quili Gu
This method implies changing the directory, it means it must be a shell method.
It can pass all its arguments to the NodeJS app then receive the list of matching branches and parse it if it's more convenient.
The file utils is too big, let's split it in separate files (already started) and require only the parts needed.
The lodash merge performed to aggregate them adds a layer that prevent IDEs to perform auto-complete anyway which is annoying.
It should be easy to run CI jobs on a repository from Gut.
Not applicable yet
The repository configuration file should contain:
There should be Gut-provided variables, e.g. Gut will replace $<variable name>
by its value.
The provided values should be at least the current branch, and each part of the branch.
There could also be a special variable to make Gut prompt the user for it (for example $ask(toto)
).
Example configuration:
{
"accounts": {
"jenkins": {
"username": "your username",
"password": "your password"
}
},
"ci": {
"jenkins": {
"package": {
"uri": "https://jenkins.mycompany.com/job/package/build",
"body": {
"parameter": [{
"name": "branch_or_tag",
"value": "$currentBranch"
},
{
"name": "version",
"value": "$currentVersion"
}
]
}
}
}
}
}
Using gut execute
without staged changes fails without clearly explaining why.
Not applicable yet
Either a specific message or maybe a flag to add all the files in the repo before committing and a validation between the git statut
and the actual commit ?
Use gut execute
with unstaged changes.
When running npm audit
, run a script to display repository-related metrics.
Not applicable yet
Example: npm audit
could show the difference in numbers of eslint warnings between the two considered commits (using bisect?).
It should be possible to force-push BUT force-push should only be allowed on branches where only the current author has already pushed.
Not applicable yet
The command thrust
should accept the parameter -f
to force-push.
The force-push should be disallowed if:
Currently, branches that were not created with Gut don't have descriptions => no baseBranch set.
This means some Gut commands fail (i.e. audit).
Not applicable yet
When trying to use the branch description and it's empty, fill it! lib/utils/branches:getBranchDescription
Create a branch using git, commit something, run gut audit -b
=> 50 commits shown. There should be one.
Not applicable yet
On a clean repository, it should be easy to undo the last n commits. The changes should then be either stashed or deleted permanently or just remain as is.
The specification is available here
When creating a PR, gut should write the URL to the branch's description. Then it should be possible to open, copy or display it.
Not applicable yet
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.