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

chore(ci): remove release epic action (backport #3996) #3997

Closed
wants to merge 1 commit into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Oct 22, 2024

Overview

The release EPIC action doesn't make sense anymore with the new arabica and mocha tags. Removing it while we work on making some updates to the release tracking.

I added the backport:v2.x tag to make sure any more v2 releases don't create issues. I didn't see a backport label for v3 yet but it would be good to apply this to that branch as well.


This is an automatic backport of pull request #3996 done by Mergify.

<!--
Please read and fill out this form before submitting your PR.

Please make sure you have reviewed our contributors guide before
submitting your
first PR.
-->

## Overview

<!--
Please provide an explanation of the PR, including the appropriate
context,
background, goal, and rationale. If there is an issue with this
information,
please provide a tl;dr and link the issue.
-->

The release EPIC action doesn't make sense anymore with the new arabica
and mocha tags. Removing it while we work on making some updates to the
release tracking.

I added the `backport:v2.x` tag to make sure any more v2 releases don't
create issues. I didn't see a backport label for v3 yet but it would be
good to apply this to that branch as well.

(cherry picked from commit 373eb9d)

# Conflicts:
#	.github/workflows/create_release_tracking_epic.yml
@mergify mergify bot added the conflicts label Oct 22, 2024
Copy link
Contributor Author

mergify bot commented Oct 22, 2024

Cherry-pick of 373eb9d has failed:

On branch mergify/bp/v2.x/pr-3996
Your branch is up to date with 'origin/v2.x'.

You are currently cherry-picking commit 373eb9d4.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by them: .github/workflows/create_release_tracking_epic.yml

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@celestia-bot celestia-bot requested review from a team, cmwaters and ninabarbakadze and removed request for a team October 22, 2024 14:53
@github-actions github-actions bot added the bot item was created by a bot label Oct 22, 2024
Copy link
Member

@ninabarbakadze ninabarbakadze left a comment

Choose a reason for hiding this comment

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

what do we want to do with this? @cmwaters seems like there's no diff

@cmwaters
Copy link
Contributor

cmwaters commented Oct 31, 2024

Yeah I think we can just close this. We may have forgotten to extend it to this long-lived branch anyway

@cmwaters cmwaters closed this Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot item was created by a bot conflicts
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants