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

Update hg actions #195

Merged
merged 2 commits into from
May 31, 2023
Merged

Update hg actions #195

merged 2 commits into from
May 31, 2023

Conversation

roivaz
Copy link
Member

@roivaz roivaz commented May 31, 2023

  • Updates versions of the actions used.
  • Remove the caching actions as actions/setup-go@v4 already has built-in caching enabled by default
  • Add an action to publish the operator catalog when changes are made to the stable channel

/kind feature
/priority important-longterm
/assign

@3scale-robot 3scale-robot added kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple sprints to complete. needs-size Indicates a PR or issue lacks a `size/foo` label and requires one. size/M Requires about a day to complete the PR or the issue. and removed needs-size Indicates a PR or issue lacks a `size/foo` label and requires one. labels May 31, 2023
@3scale-robot 3scale-robot requested review from raelga and slopezz May 31, 2023 09:34
@roivaz
Copy link
Member Author

roivaz commented May 31, 2023

/ok-to-test

@3scale-robot 3scale-robot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label May 31, 2023
@slopezz
Copy link
Member

slopezz commented May 31, 2023

@roivaz Can you please update the release doc https://github.com/3scale-ops/marin3r/blob/main/docs/release.md according to the new procedure of both:

  • Alpha (single PR, manual executions of the 2 tagets)
  • Stable (2 PRs on specific order with specific target each)
    ?

@roivaz
Copy link
Member Author

roivaz commented May 31, 2023

let's first test that this actually works... I'll update the docs in an upcoming PR 😅

@slopezz
Copy link
Member

slopezz commented May 31, 2023

/lgtm

@3scale-robot 3scale-robot added the lgtm Indicates that a PR is ready to be merged. label May 31, 2023
@3scale-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: f0f99deabe2eea519833e5bfcbd1e167e6de9c43

@roivaz
Copy link
Member Author

roivaz commented May 31, 2023

/approve

@3scale-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: roivaz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@3scale-robot 3scale-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 31, 2023
@3scale-robot 3scale-robot merged commit f9644ba into main May 31, 2023
@3scale-robot 3scale-robot deleted the update-hg-actions branch May 31, 2023 09:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple sprints to complete. size/M Requires about a day to complete the PR or the issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants