-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New commands, bug fixes and support for aliases #54
Conversation
… will be displayed.
README.md
Outdated
@@ -98,6 +98,12 @@ CLI options: | |||
--scope Restricts the command to packages which names match the given glob pattern. | |||
|
|||
Default: null | |||
|
|||
--packages-prefix The common name of the packages. The prefix will be removed from packages' names in order to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this a CLI config option? Do you expect anyone to use it? I don't. If anywhere – this is for mgit.json
only.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed in d95291a.
Since you're adding the |
Could we clean up the mess after merging these changes? I would like to avoid bigger PR than we have now. After merging we will be able to decide how these commands should work and what should do. |
Yes, we can. But if you wanted to add |
README.md
Outdated
@@ -255,6 +254,62 @@ Example: | |||
mgit save-hashes | |||
``` | |||
|
|||
### status | |||
##### Available also `st` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That shouldn't be a heading. Don't use semantical markup for styling reasons.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can have ### stats (alias: st)
.
Please also add a screenshot.
README.md
Outdated
In order to save space in your terminal, you can define the `packagesPrefix` option in your configuration file. | ||
The prefix will be removed from packages' names. Full names of packages aren't needed so we can cat the names. | ||
|
||
### diff |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a screenshot.
@@ -21,57 +21,55 @@ module.exports = { | |||
execute( data ) { | |||
const log = require( '../utils/log' )(); | |||
|
|||
return new Promise( ( resolve, reject ) => { | |||
const destinationPath = path.join( data.options.packages, data.repository.directory ); | |||
const destinationPath = path.join( data.options.packages, data.repository.directory ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you change anything in this file or is it just a code style?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If so – why changing anything?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
execCommand.execute( getExecData( 'git rev-parse HEAD' ) ) | ||
.then( execResponse => { | ||
const commitHash = execResponse.logs.info[ 0 ]; | ||
return execCommand.execute( getExecData( 'git rev-parse HEAD' ) ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The same question as about bootstrap
.
@@ -22,82 +22,77 @@ module.exports = { | |||
const bootstrapCommand = require( './bootstrap' ); | |||
const execCommand = require( './exec' ); | |||
|
|||
return new Promise( ( resolve, reject ) => { | |||
const destinationPath = path.join( data.options.packages, data.repository.directory ); | |||
const destinationPath = path.join( data.options.packages, data.repository.directory ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The same – what are these changes?
And the One line per repo would be better. Something like "HEAD is now at f1131bc... Merge pull request #33 from ckeditor/t/32" will be fine. |
Ok, mgit should not show staged files as modified also. I'll correct it. |
👍 |
I've been using these new commands for some time and they are great. No more issues found. |
Suggested merge commit message (convention)
Feature: Introduced new commands and fixes bugs related to invalid displayed errors. Closes #2. Closes #45. Closes #49. Closes #52.
checkout
– changes branches in repositories according to the configuration file (see Introduce mgit checkout #52),diff
– prints changes from all repositories (see Add status command #2),status
– prints a table which contains useful information about the status of repositories (see Add status command #2).Unhandled promise
error (see Unhandled promise: TypeError: msg.trim is not a function #49).st
=>status
,co
=>checkout
).Additional information
On the occasion, I simplified the promises flow in the commands.