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

Detect feature branches written with a different format #94

Merged
merged 1 commit into from
Jan 30, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions ci/publish-tfgen-package
Original file line number Diff line number Diff line change
Expand Up @@ -43,13 +43,17 @@ if [[ "${TRAVIS_OS_NAME:-}" == "linux" ]]; then

NPM_TAG="dev"

# We use the "features/" prefix on branches that we want to build and publish for doing
# cross repo work. But in this case, we don't want to publish over "dev", since the bits
# We use the "features/" and "feature-" prefix on branches that we want to build and publish for
# doing cross repo work. But in this case, we don't want to publish over "dev", since the bits
# could be totally busted and the dev tag tracks master.
if [[ "${TRAVIS_BRANCH:-}" == features/* ]]; then
NPM_TAG=$(echo "${TRAVIS_BRANCH}" | sed -e 's|^features/|feature-|g')
fi

if [[ "${TRAVIS_BRANCH:-}" == feature-* ]]; then
NPM_TAG=$(echo "${TRAVIS_BRANCH}")
fi

# If the package doesn't have a pre-release tag, use the tag of latest instead of
# dev. NPM uses this tag as the default version to add, so we want it to mean
# the newest released version.
Expand Down