-
Notifications
You must be signed in to change notification settings - Fork 651
Uploading AppVeyor artifacts fails when doing Pull Request #1088
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
Comments
gep13
added a commit
to gep13/GitVersion
that referenced
this issue
Nov 18, 2016
- Only do this when on the master branch of main GitVersion repo, and when it is NOT a PullRequest - Ensure that releasenotes.md exists prior to attempting upload
gep13
added a commit
to gep13/GitVersion
that referenced
this issue
Nov 18, 2016
- Only do this when on the master branch of main GitVersion repo, and when it is NOT a PullRequest - Ensure that releasenotes.md exists prior to attempting upload
JakeGinnivan
added a commit
that referenced
this issue
Nov 26, 2016
Control when an attempt is made to upload releasenotes.md
Wasn't this fixed by @JakeGinnivan over the last weekend? |
This should be fixed by #1093 |
@pascalberger agreed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is due to the fact that an attempt is made to upload the releasenotes.md file, however, this file does not exist, since it will ONLY be created when a GitHub Token exists, and this will only be the case when running on the master branch, as this is the only time the Environment Variable will exist.
The text was updated successfully, but these errors were encountered: