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.

Sign up for GitHub

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

Jump to bottom

Github Actions: remove legacy step from integration pipeline #472

Merged
merged 1 commit into from Feb 5, 2021
Merged

Github Actions: remove legacy step from integration pipeline #472

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 1 addition & 5 deletions .github/workflows/integration.yml
View file
Open in desktop
Expand Up @@ -147,10 +147,6 @@ jobs:
repository: "${{ needs.configure.outputs.repo-name }}"
persist-credentials: false

- name: Get the Liqo version to be released
id: version
run: echo "version::${GITHUB_REF/refs\/tags\//}" >> $GITHUB_ENV

- name: Get the latest Liqo release
uses: pozetroninc/github-action-get-latest-release@v0.5.0
id: last-release
Expand Down Expand Up @@ -237,4 +233,4 @@ jobs:

I'm waiting for a Liqo member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test.

Once the patch is verified, the new status will be reflected by the ok-to-test label.
Once the patch is verified, the new status will be reflected by the ok-to-test label.