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

Reusable workflows #1278

Merged
merged 2 commits into from
May 12, 2022

Conversation

NikitaSkrynnik
Copy link
Contributor

Description

Issue link

networkservicemesh/.github#4

How Has This Been Tested?

  • Added unit testing to cover
  • Tested manually
  • Tested by integration testing
  • Have not tested

Types of changes

  • Bug fix
  • New functionallity
  • Documentation
  • Refactoring
  • CI

@NikitaSkrynnik NikitaSkrynnik force-pushed the reusable-workflows branch 3 times, most recently from be924fc to 08d7b86 Compare May 5, 2022 14:21
Signed-off-by: Nikita Skrynnik <nikita.skrynnik@xored.com>
Signed-off-by: Nikita Skrynnik <nikita.skrynnik@xored.com>
@NikitaSkrynnik NikitaSkrynnik marked this pull request as ready for review May 12, 2022 09:06
Copy link
Member

@denis-tingaikin denis-tingaikin left a comment

Choose a reason for hiding this comment

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

LGTM 🚀

GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
MAXIMUM_RETRIES: 25
if: ${{ github.event.workflow_run.conclusion == 'success' && github.actor == 'nsmbot'}}
uses: networkservicemesh/.github/.github/workflows/automerge.yaml@main
Copy link
Member

Choose a reason for hiding this comment

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

Do we want to depend on a branch here rather than a specific point?

I can see tradeoffs either way... so the real question is 'have we thought it through' ?

Copy link
Member

@denis-tingaikin denis-tingaikin May 12, 2022

Choose a reason for hiding this comment

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

I see next pros/cons

pros:

  • we're always up to date.

cons:

  • ci for previous could be unstable.

In my mind the best option is:

  1. use @main version by default.
  2. change @main version to the point on the release.

I think we can address this in the v1.5.0.

Thoughts?

Copy link
Member

Choose a reason for hiding this comment

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

Sounds good :)

Copy link
Member

@denis-tingaikin denis-tingaikin May 12, 2022

Choose a reason for hiding this comment

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

@edwarnicke I've created a ticket for v1.5.0 networkservicemesh/.github#6

@edwarnicke
Copy link
Member

Overall other than my branch vs commit comment above, I'm good with this :)

@edwarnicke edwarnicke merged commit ef08ddb into networkservicemesh:main May 12, 2022
@NikitaSkrynnik NikitaSkrynnik deleted the reusable-workflows branch June 19, 2022 23:39
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.

3 participants