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

Merge next into master #136

Merged
merged 29 commits into from
Sep 23, 2024
Merged

Merge next into master #136

merged 29 commits into from
Sep 23, 2024

Conversation

reeshika-h
Copy link
Contributor

@reeshika-h reeshika-h commented Sep 20, 2024

To resolve conflicts in back merge(next<-master)

@reeshika-h reeshika-h requested a review from a team as a code owner September 20, 2024 04:54
Copy link

We regret to inform you that you are currently not able to merge your changes into the master branch due to restrictions applied by our SRE team. To proceed with merging your changes, we kindly request that you create a pull request from the next branch. Our team will then review the changes and work with you to ensure a successful merge into the master branch.

@reeshika-h reeshika-h marked this pull request as draft September 20, 2024 04:55
@reeshika-h reeshika-h changed the base branch from master to next September 23, 2024 07:50
@reeshika-h reeshika-h marked this pull request as ready for review September 23, 2024 07:51
Copy link
Contributor

@harshithad0703 harshithad0703 left a comment

Choose a reason for hiding this comment

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

Approved

@reeshika-h reeshika-h merged commit a4040c4 into next Sep 23, 2024
7 of 8 checks passed
@reeshika-h reeshika-h deleted the merge-next-into-master branch September 23, 2024 07:52
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.

5 participants