If I do mergify -V without having configured first, I won't get any answer and the tool tries to get me to configure instead

Ora has more standard options and we can mutate texts easily.
https://github.com/sindresorhus/ora#readme

Once configured, if I simply run mergify, nothing happens.
It would be great to have a default.

Maybe a tad out of scope at the moment, but it would be nice to have some small utils to actually review merge requests.

For example, one thing that I usually do when reviewing is git reset HEAD^ or using the commit hash of the first commit in the MR when there are several commits (and I have to do a git log and it's sometimes annoying). That way I can see all the changes inline in my IDE for instance, which is better IMO than looking at diffs and truncated files on Gitlab.

Something to think about. The other enhancements proposed until now should have priority I think.

I actually use 3 different gitlab instances :

• .com for open source / personal work
• local instance at my day job
• local instance at another job

It would be great to be able to select profiles, or at least use several instances at once in Mergify.

Right now I can only see the merge requests for one instance :).

At the moment, the project uses flags(options) to issues commands mergify -v, ...

Flags should be more used for options (for example to disable certificates verification, . . .).

Commands seem more relevant for things like submitted / review, . . .

For exampple, something like

$ mergify configure -s sounds more logical than mergify -sc.

In addition, commands could have autocompletion.

When we want to modify something internal from mergify we will have some users that still have the previous version. To not break on update with for instance config changes I suggest we use a post install script to verify that mergify can run, otherwise perform migration.

If I try to configure mergify, I am constantly getting:

I looked into the doFetch class and it looks like both private_token and domain_name are not known to the function.

If I understand the code correctly, I think I know what is happening

• User runs configure - https://github.com/RamonGebben/mergify/blob/master/index.js#L97
• User enters info
• Infos are verified https://github.com/RamonGebben/mergify/blob/master/index.js#L76
  • Using doFetch
  • doFetch reads the config https://github.com/RamonGebben/mergify/blob/master/lib/doFetch/index.js#L5
• If verify works, the config is written using writeConfig https://github.com/RamonGebben/mergify/blob/master/index.js#L120

Basically, we are trying to read the config before it is written, which explains why I am getting errors.

The message could look something like this:
The addition here is the passed status between the status of the MR and if it doesn't have conflicts.

[open|passed|can be merged]
  !82: Integration feedback into design
    Assignee: alxbrg
    Author: RamonGebben
    Source: foobar_design
    Target: master

    https://gitlab.com/Sensorfact/frontend/nucleus/merge_requests/82

To make the tools more valuable we should fetch approval and CI status to give actionable suggestions on MR's.

Not something you might want to fix now, but I just wanted to let you know that mergify does not work if you are behind a proxy at the moment :).
(Even with HTTP_PROXY and other variables set).

Once I have a config file, there is no way for me to change the config anymore without manually editing the file.

I don't really want to give you write access if I don't have to :).

Right now token that don't have API access get accepted and the program crashes.

• Program should not crash on Unauthorised but should show nice error
• README should be updated explaining that private token should have API access
• Add --verify command to verify at any time
• Maybe fetch username and let user confirm that this is her username.

To see all merge requests authored by you and which are approved when approval status is a thing. When it's not we'll have to look for the "👍 "

Because the installation requires some skippable steps I'd like to add a --configure command.
This command would prompt the user to input:

• Gitlab URL
• Private token
• User ID
• other stuff we might need in the future

I think creating a .config when it doesn't exist would suffice and JSON should be the format.

This is what I get when I try to configure my work gitlab. I get certificate issues

[jlengrand@rn07t1c18:~/IdeaProjects/mergify]$ node index.js -c
? What is your Gitlab User ID? 6011
? What private token shall we use? [hidden]
? On what domain is your Gitlab instance? gitlab.company.net

🙀  Oh no, could not complete verify. Please review your config
{ FetchError: request to https://gitlab.company.net/api/v4/users/6011 failed, reason: unable to verify the first certificate
    at ClientRequest.<anonymous> (/Users/jlengrand/IdeaProjects/mergify/node_modules/node-fetch/lib/index.js:1393:11)
    at ClientRequest.emit (events.js:180:13)
    at TLSSocket.socketErrorListener (_http_client.js:395:9)
    at TLSSocket.emit (events.js:180:13)
    at emitErrorNT (internal/streams/destroy.js:64:8)
    at process._tickCallback (internal/process/next_tick.js:178:19)
  message: 'request to https://gitlab.company.net/api/v4/users/6011 failed, reason: unable to verify the first certificate',
  type: 'system',
  errno: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE',
  code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE' }

So it looks like at the moment I can't use mergify at work. I'll look into that too.