No way to manually provide pull_request information?

[dclowd9901]

Hi,

In our setup, we use workflow_dispatch to manually kick off our cypress runs. Because of this, the workflow dispatches are run without a pull_request or pull_request-like context. Because of this (I believe), our dashboard does not contain any PR information related to test runs. Is there a way to manually provide PR information to the Cypress github action so that we can associate those runs with their appropriate PRs?

[bahmutov]

Great question, but running on workflow_dispatch ... does not have a pull request, right? So what would the PR info even be in this case?

[dclowd9901]

It’s true. We have a workaround that manually digs up the pull request via api call. I was just hoping there was a way to manually provide that information.

…

On Fri, Apr 30, 2021 at 1:52 PM Gleb Bahmutov ***@***.***> wrote: Great question, but running on workflow_dispatch ... does not have a pull request, right? So what would the PR info even be in this case? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#350 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKA2EVJ2AHDKVFLMTQ3DRDTLMKB3ANCNFSM42VJ7DWQ> .

[bahmutov]

I don’t mind working on this, we had this question come up often enough

…

Sent from my iPhone

On Apr 30, 2021, at 18:27, David Drew ***@***.***> wrote:  It’s true. We have a workaround that manually digs up the pull request via api call. I was just hoping there was a way to manually provide that information. On Fri, Apr 30, 2021 at 1:52 PM Gleb Bahmutov ***@***.***> wrote: > Great question, but running on workflow_dispatch ... does not have a pull > request, right? So what would the PR info even be in this case? > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#350 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAKA2EVJ2AHDKVFLMTQ3DRDTLMKB3ANCNFSM42VJ7DWQ> > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[dclowd9901]

That would be awesome! Thanks for all the great work! On Fri, Apr 30, 2021 at 3:31 PM Gleb Bahmutov ***@***.***> wrote:

…

I don’t mind working on this, we had this question come up often enough Sent from my iPhone > On Apr 30, 2021, at 18:27, David Drew ***@***.***> wrote: > >  > It’s true. We have a workaround that manually digs up the pull request via > api call. I was just hoping there was a way to manually provide that > information. > > On Fri, Apr 30, 2021 at 1:52 PM Gleb Bahmutov ***@***.***> > wrote: > > > Great question, but running on workflow_dispatch ... does not have a pull > > request, right? So what would the PR info even be in this case? > > > > — > > You are receiving this because you authored the thread. > > Reply to this email directly, view it on GitHub > > < #350 (comment) >, > > or unsubscribe > > < https://github.com/notifications/unsubscribe-auth/AAKA2EVJ2AHDKVFLMTQ3DRDTLMKB3ANCNFSM42VJ7DWQ > > > . > > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub, or unsubscribe. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#350 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKA2EVBOQVOZ3Y4JL26DM3TLMVTLANCNFSM42VJ7DWQ> .

[Sporradik]

We would also really appreciate this feature and I'm curious if there is any update on this.

We are trying to do something similar using repository_dispatch, where we can provide a payload to configure a pull request number.

We have a prototype working where we use repository_dispatch trigger adding a label to a PR and then the label trigger kicks off cypress. However, this intermediate label step is quite slow and it would be nice to trigger cypress directly in a way that passes our required PR checks.

[MikeMcC399]

• See https://github.com/cypress-io/github-action#automatic-pr-number--url-detection

[dclowd9901]

I’ve since moved to a position where we’re using Jenkins instead of GHA (groan), but thanks for moving this forward and out!