Workflow for the running tests

[omsuneri]

@walterbender I had created a github workflow for running jest test suites whenever a PR is raised please review this
also this workflow creates a comment on the PR about the test result with the log of failed test suites
which the author need to take note of after raising a PR.

[omsuneri]

@walterbender what i found is that the test is runing beautifully on my fork and here too but the only thing here we dont get is the comment on the PR which is i guess more important but i m trying to get the result done

[walterbender]

Looks good.

[omsuneri]

@walterbender thanks !! i m working on the comment thing too but getting stuck somewhere with the github tokens can you can review the error in the workflow log i got that we need to add some secret PAT(personal access token in the workflow) which i m investigating will be get done soon

[walterbender]

I think Ibiam may have recently dealt with PAT issues on GitHub. Maybe ask in the #sugar channel on Matrix?

[omsuneri]

@walterbender I found that I need to have the write access over the musicblocks repo in order to add the PAT in secrets and variables for our actions can you please give me the rights to access the same
I need the setting access for the repo currently I m having member but that doesn't allows me to do changes in the secret and variables of action workflow

[chimosky]

@walterbender what i found is that the test is runing beautifully on my fork and here too but the only thing here we dont get is the comment on the PR which is i guess more important but i m trying to get the result done

From the screenshot above, it looks like there's a comment on your fork, if that's the case then it works.

The reason you don't get a comment here is because this hasn't been merged.

If the workflow needs a particular secret, that's when we'll add it to this repo and point the workflow to that, else it'll work fine once this is merged.

[omsuneri]

@chimosky as for ss I made two branches one on mb master and other with changes in workflow still that works as I don't merged the changes there too so think it must work here as it does there too

[omsuneri]

@chimosky i get from your point that first we should merge this first then check if its working or not if not then need to add the secrets am i right ?

[omsuneri]

@walterbender I found a cache with this workflow as it is currently running test on the changes but we want that the test must be run on the merged changes like the workflow must assume that if the changes are merged then what might be the potential failures in the test so I redesign the test workflow and its working absolutely fine with my fork
updated in 187c04d

[omsuneri]

@walterbender I request you to merge this as if it works expectedly after merging then fine and if not we can add Personal access tokens in the workflow for the comment part

[walterbender]

Let's keep an eye on this

[omsuneri]

@walterbender sure will take a look over it 🙂