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 #3996

Merged
merged 1 commit into from
Oct 22, 2024
Merged

chore(ci): remove release epic action #3996

merged 1 commit into from
Oct 22, 2024

Conversation

MSevey
Copy link
Member

@MSevey MSevey commented Oct 21, 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.

@MSevey MSevey added WS: V3 3️⃣ item is directly relevant to the v3 hardfork backport:v2.x PR will be backported automatically to the v2.x branch upon merging labels Oct 21, 2024
@MSevey MSevey self-assigned this Oct 21, 2024
@MSevey MSevey requested a review from a team as a code owner October 21, 2024 21:00
@MSevey MSevey requested review from rach-id and evan-forbes and removed request for a team October 21, 2024 21:00
@celestia-bot celestia-bot requested a review from a team October 21, 2024 21:00
Copy link
Contributor

coderabbitai bot commented Oct 21, 2024

📝 Walkthrough

Walkthrough

The pull request involves the deletion of the GitHub Actions workflow file .github/workflows/create_release_tracking_epic.yml. This workflow was designed to trigger upon the release of a new version and was responsible for creating an EPIC in the devops repository and notifying the devops team via Slack. The workflow included a job that utilized a reusable workflow from another repository and accepted specific parameters related to the release event.

Changes

File Path Change Summary
.github/workflows/create_release_tracking_epic.yml Deleted workflow defining "Create Release Tracking Epic"

Possibly related PRs

Suggested reviewers

  • staheri14
  • evan-forbes
  • rootulp
  • cmwaters
  • ninabarbakadze

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 9322d29 and 7e3e28f.

📒 Files selected for processing (1)
  • .github/workflows/create_release_tracking_epic.yml (0 hunks)
💤 Files with no reviewable changes (1)
  • .github/workflows/create_release_tracking_epic.yml

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Collaborator

@rootulp rootulp left a comment

Choose a reason for hiding this comment

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

We haven't created a v3.x release branch yet but it will contain this commit b/c v3.x will be based on main

@rootulp rootulp enabled auto-merge (squash) October 22, 2024 14:42
@rootulp rootulp merged commit 373eb9d into main Oct 22, 2024
34 checks passed
@rootulp rootulp deleted the remove-release-epic branch October 22, 2024 14:53
mergify bot pushed a commit that referenced this pull request Oct 22, 2024
<!--
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:v2.x PR will be backported automatically to the v2.x branch upon merging external WS: V3 3️⃣ item is directly relevant to the v3 hardfork
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants