Add a new environment variable which has the same value as `TRAVIS_BRANCH` or `TRAVIS_PULL_REQUEST_BRANCH` depending on the context
The addition of `$TRAVIS_PULL_REQUEST_BRANCH` from https://github.com/travis-ci/travis-ci/issues/1633 is nice, but it is still a bit difficult to get the name of the _current_ branch name from both PUSH and PR builds. The current workaround I have is this, which is not great: ``` export BRANCH=$(if [ "$TRAVIS_PULL_REQUEST" == "false" ]; then echo $TRAVIS_BRANCH; else echo $TRAVIS_PULL_REQUEST_BRANCH; fi) ``` Instead of having users script this, I suggest adding an environment variable `$TRAVIS_CURRENT_BRANCH`.
Posted by HelloGrayson on Sep 29, 2016, 7:03 PM
Tags
Related issues
- This is the biggest problem with contracts, there's simply no way to actually say "please always execute this check".
- I don't disagree with you on this, I worked my whole life in corporate and haven't worked as a OSS maintainer before, though I will _and ...
- the new VSCode UI, looks cute, i don't like it.
- I've been working on my own private harness for the past 8 months, and I've been collecting ideas from such repos I've stumbled upon.
- The way AI is able to interact with outside resources is pretty impressive, but the quality of code it produces to me is still questionab...
- Add PR-style review comments in Git Diff UI that feed into the active agent thread
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
ux (Software)
This is the biggest problem with contracts, there's simply no way to actually say "please always execute this check".
I don't disagree with you on this, I worked my whole life in corporate and haven't worked as a OSS maintainer before, though I will _and ...
the new VSCode UI, looks cute, i don't like it.
I've been working on my own private harness for the past 8 months, and I've been collecting ideas from such repos I've stumbled upon.
The way AI is able to interact with outside resources is pretty impressive, but the quality of code it produces to me is still questionab...
Add PR-style review comments in Git Diff UI that feed into the active agent thread
Thanks for indulging me so far, by the way, I really appreciate this discussion, it's very stimulating.
Migrate GDScript to the GDExtension mechanism and overhaul the implementation
Add a new environment variable which has the same value as `TRAVIS_BRANCH` or `TRAVIS_PULL_REQUEST_BRANCH` depending on the context
The addition of `$TRAVIS_PULL_REQUEST_BRANCH` from https://github.com/travis-ci/travis-ci/issues/1633 is nice, but it is still a bit difficult to get the name of the _current_ branch name from both PUSH and PR builds. The current workaround I have is this, which is not great: ``` export BRANCH=$(if [ "$TRAVIS_PULL_REQUEST" == "false" ]; then echo $TRAVIS_BRANCH; else echo $TRAVIS_PULL_REQUEST_BRANCH; fi) ``` Instead of having users script this, I suggest adding an environment variable `$TRAVIS_CURRENT_BRANCH`.
Comments (0)
No comments yet. Start the discussion.