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

Squashed and merged staging into master, to prevent conflicts #73

Merged
merged 1 commit into from
Jan 17, 2024

Conversation

LiorAgnin
Copy link
Member

subj

Copy link

vercel bot commented Jan 17, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
fuse-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 17, 2024 7:43am

@emmaodia
Copy link
Contributor

@leonprou You want to merge the branch straight into master?
staging is the same as master; we use staging to ensure that nothing breaks in prod.
Do I go ahead and merge or do we set the base to staging?

@LiorAgnin
Copy link
Member Author

@leonprou You want to merge the branch straight into master? staging is the same as master; we use staging to ensure that nothing breaks in prod. Do I go ahead and merge or do we set the base to staging?

@emmaodia Yes, I did that to ensure we haven't overlooked any commits merged into Staging.

@LiorAgnin LiorAgnin merged commit 4995288 into master Jan 17, 2024
3 checks passed
@LiorAgnin LiorAgnin deleted the feat/squash_and_merge_staging branch January 22, 2024 15:07
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.

None yet

2 participants