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

Use GITHUB_REF_NAME as name of push branch; fix error in branch detection [citest skip] #64

Merged

Conversation

richm
Copy link
Contributor

@richm richm commented Jul 27, 2022

We need to get the name of the branch to which CHANGELOG.md was pushed.
For now, it looks as though GITHUB_REF_NAME is that name. But don't
trust it - first, check that it is main or master. If not, then use
a couple of other methods to determine what is the push branch.

Signed-off-by: Rich Megginson rmeggins@redhat.com

…tion [citest skip]

We need to get the name of the branch to which CHANGELOG.md was pushed.
For now, it looks as though `GITHUB_REF_NAME` is that name.  But don't
trust it - first, check that it is `main` or `master`.  If not, then use
a couple of other methods to determine what is the push branch.

Signed-off-by: Rich Megginson <rmeggins@redhat.com>
@richm richm requested a review from ueno as a code owner July 27, 2022 15:13
Copy link
Contributor

@nhosoi nhosoi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@richm richm merged commit 00a08ff into linux-system-roles:master Jul 27, 2022
@richm richm deleted the use-GITHUB_REF_NAME-for-push-branch branch July 27, 2022 17:59
richm added a commit to richm/linux-system-roles-vpn that referenced this pull request Sep 19, 2022
[1.3.6] - 2022-09-19
--------------------

### New Features

- Various improvements required to connect to a managed remote host (linux-system-roles#65)

Add support for the parameters shared_key_content, leftid, rightid, ike, esp, type, ikelifetime, salifetime, retransmit_timeout, dpddelay, dpdtimeout, dpdaction, leftupdown

### Bug Fixes

- Check for /usr/bin/openssl on controller - do not use package_facts (linux-system-roles#66)

Check for existence of openssl without using sudo on the controller
Basically, any task, even package_facts:, will use sudo if using
become=true - so just use "exists" test to check for /usr/bin/openssl

### Other Changes

- Fix a bash bug in changelog_to_tag.yml, which unexpectedly expanded "*" (linux-system-roles#62)

- changelog_to_tag action - support other than "master" for the main branch name, as well (linux-system-roles#63)

- Use GITHUB_REF_NAME as name of push branch; fix error in branch detection [citest skip] (linux-system-roles#64)

We need to get the name of the branch to which CHANGELOG.md was pushed.
For now, it looks as though `GITHUB_REF_NAME` is that name.  But don't
trust it - first, check that it is `main` or `master`.  If not, then use
a couple of other methods to determine what is the push branch.

Signed-off-by: Rich Megginson <rmeggins@redhat.com>
richm added a commit to richm/linux-system-roles-vpn that referenced this pull request Sep 19, 2022
[1.4.0] - 2022-09-19
--------------------

- Various improvements required to connect to a managed remote host (linux-system-roles#65)

Add support for the parameters shared_key_content, leftid, rightid, ike, esp, type, ikelifetime, salifetime, retransmit_timeout, dpddelay, dpdtimeout, dpdaction, leftupdown

- Check for /usr/bin/openssl on controller - do not use package_facts (linux-system-roles#66)

Check for existence of openssl without using sudo on the controller
Basically, any task, even package_facts:, will use sudo if using
become=true - so just use "exists" test to check for /usr/bin/openssl

- Fix a bash bug in changelog_to_tag.yml, which unexpectedly expanded "*" (linux-system-roles#62)

- changelog_to_tag action - support other than "master" for the main branch name, as well (linux-system-roles#63)

- Use GITHUB_REF_NAME as name of push branch; fix error in branch detection [citest skip] (linux-system-roles#64)

We need to get the name of the branch to which CHANGELOG.md was pushed.
For now, it looks as though `GITHUB_REF_NAME` is that name.  But don't
trust it - first, check that it is `main` or `master`.  If not, then use
a couple of other methods to determine what is the push branch.

Signed-off-by: Rich Megginson <rmeggins@redhat.com>
richm added a commit that referenced this pull request Sep 19, 2022
[1.4.0] - 2022-09-19
--------------------

- Various improvements required to connect to a managed remote host (#65)

Add support for the parameters shared_key_content, leftid, rightid, ike, esp, type, ikelifetime, salifetime, retransmit_timeout, dpddelay, dpdtimeout, dpdaction, leftupdown

- Check for /usr/bin/openssl on controller - do not use package_facts (#66)

Check for existence of openssl without using sudo on the controller
Basically, any task, even package_facts:, will use sudo if using
become=true - so just use "exists" test to check for /usr/bin/openssl

- Fix a bash bug in changelog_to_tag.yml, which unexpectedly expanded "*" (#62)

- changelog_to_tag action - support other than "master" for the main branch name, as well (#63)

- Use GITHUB_REF_NAME as name of push branch; fix error in branch detection [citest skip] (#64)

We need to get the name of the branch to which CHANGELOG.md was pushed.
For now, it looks as though `GITHUB_REF_NAME` is that name.  But don't
trust it - first, check that it is `main` or `master`.  If not, then use
a couple of other methods to determine what is the push branch.

Signed-off-by: Rich Megginson <rmeggins@redhat.com>

Signed-off-by: Rich Megginson <rmeggins@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants