Skip to content
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

Provide access to the pull request's body #9302

Open
nex3 opened this issue Mar 6, 2018 · 8 comments
Open

Provide access to the pull request's body #9302

nex3 opened this issue Mar 6, 2018 · 8 comments

Comments

@nex3
Copy link

nex3 commented Mar 6, 2018

It's useful to be able to send messages to build infrastructure via the pull request message—things like [ci skip], but with semantics specific to the project at hand. It would be really useful if, for pull request builds, Travis provided access to the pull request message as an environment variable, file on disk, or something similar.

It's possible to get this via the GitHub API, and in practice this is what we do in the sass-spec repo. However, this is very flaky; we regularly run into GitHub rate limits which prevent the logic from working correctly. Since Travis already has access to the information about the pull request, it would be great if it could provide that information to the build.

@BanzaiMan
Copy link
Contributor

Hello. Am I correct to assume that you mean "title" of the PR, rather than "message", that you want access to? (https://developer.github.com/v3/pulls/#get-a-single-pull-request)

@BanzaiMan
Copy link
Contributor

If so, this is a duplicate of #9288.

@nex3
Copy link
Author

nex3 commented Mar 22, 2018

No, we need access to what the GitHub API refers to as the "body". For example, in sass/sass-spec#1229, we want to be able to look for [skip dart-sass] and skip tests accordingly.

@BanzaiMan BanzaiMan changed the title Provide access to the pull request's message Provide access to the pull request's body Mar 22, 2018
@BanzaiMan
Copy link
Contributor

Thanks for the clarification.

@nex3
Copy link
Author

nex3 commented Jun 21, 2018

Not to be a bother, but we're still seeing a lot of flakes that this would let us avoid.

@BanzaiMan BanzaiMan self-assigned this Sep 22, 2018
@nevercast
Copy link

nevercast commented Sep 26, 2019

Is there any intent to visit this in the near future? I too would like to add CI instructions in the body of the PR request to not dirty up the PR title.

@nex3
Copy link
Author

nex3 commented Oct 25, 2019

This is still causing substantial trouble for the Sass project.

@fjahr
Copy link

fjahr commented Apr 4, 2020

This would be very helpful for me as well, much more than the title.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants