-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
Add BHIsPullRequest #79
Comments
Should probably be possible. @RamblingCookieMonster if you think this is useful I can give it a try, doesn't look like it should be too hard. |
well whatdya know, I now found myself needing to know if I'm in a PR or not, so I guess I'm gonna write this one too |
@bryan5989 what Ci system do you use? |
Mostly appveyor, sometimes travis
…On Fri, Jun 14, 2019, 2:22 PM Peter Bajurny ***@***.***> wrote:
@bryan5989 <https://github.com/bryan5989> what Ci system do you use?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#79?email_source=notifications&email_token=ABLQ6JJWBBUMBSTLEZAI46DP2POWNA5CNFSM4F7TXAOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXXS4EY#issuecomment-502214163>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABLQ6JP6KFZBFURYVUDGTGDP2POWNANCNFSM4F7TXAOA>
.
|
Well that's two environments I don't use, so that'll be two more environments that some can actually validate |
Not sure if there is a reliable way to determine if a commit is a pull request from within all CI environments, but would like to see the option explored
Use case, I don't want to deploy on Pull requests, but I don't want disable the Pull webhook in GitHub
I have all my deploy logic in a psdeply script and would like to control deploy on pull request. Reason is appveyor does not resolve secrets on PR (for public repo anyways) and thus deploy can't work. (deploy to psgallery) <- I sometimes deploy stable (-dev##) versions to psgallery
Semi-unrelated: Is there a way to tell appveyor to not build a branch if there is a pull request open (I want to avoid the double build on PR update)
The text was updated successfully, but these errors were encountered: