[FEATURE] automate `branch` and `commit hash` CLI options about reassure HOT 8 CLOSED

@ShaswatPrabhat Thanks for working on this. I'm not sure I understand your question though.

The data flow between the packages should be the same as is now for branch and commit-hash CLI options. The difference should be that when Reassure 'measure' command does not receive either branch or commit-hash option then it tries to get the missing value(s) from Git if possible.

from reassure.

A good place for checking these values is the very beginning of "run" method in measure.ts in CLI package

from reassure.

Resolved by #211

from reassure.

Picking this up please.

Will it be a good idea to keep these values as default in measure.ts after auto detecting git based branches ?

from reassure.

@mdjastrzebski there were a couple of things I wanted to check:

• Which way of spawning a child process would be preferable ? Right now I am looking at child_process.fork, but any notes regarding the same?
• With the above approach the function becomes an IIFE like so:

  const simpleGit = require('simple-git');
  const git = simpleGit({ baseDir: process.cwd() });
  const branch = await git.revparse(['--abbrev-ref', 'HEAD']);
  const commitHash = await git.revparse(['HEAD']);
  process.send({ branch, commitHash });
})();

Please let me know if this is what you had thought of

from reassure.

I've looked more into the simple-git package. It seems that it's actually invoking git binary by itself, so we can give it a try.

from reassure.

This is how it is shaping up @mdjastrzebski .

Not very happy with the IIFE .

Can we not have a simple await based function call immediately in run() method ? Do we need a fork at all

from reassure.

And an alternative way

from reassure.