-
Notifications
You must be signed in to change notification settings - Fork 351
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
No way to manually provide pull_request information? #350
Comments
Great question, but running on |
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>
.
|
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.
|
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>
.
|
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 We have a prototype working where we use |
I’ve since moved to a position where we’re using Jenkins instead of GHA (groan), but thanks for moving this forward and out! |
Hi,
In our setup, we use
workflow_dispatch
to manually kick off our cypress runs. Because of this, the workflow dispatches are run without apull_request
orpull_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?The text was updated successfully, but these errors were encountered: