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

Prepare Goose for 0.6.0 release #196

Merged
merged 2 commits into from
Oct 4, 2024
Merged

Prepare Goose for 0.6.0 release #196

merged 2 commits into from
Oct 4, 2024

Conversation

olttwa
Copy link
Member

@olttwa olttwa commented Sep 29, 2024

No description provided.

@olttwa olttwa self-assigned this Sep 29, 2024
@olttwa olttwa requested a review from siripr4 September 29, 2024 10:45
Copy link
Contributor

@alishamohanty alishamohanty left a comment

Choose a reason for hiding this comment

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

Can you separate the periodic->cron changes and release changes into different commits?

@olttwa
Copy link
Member Author

olttwa commented Oct 3, 2024

Can you separate the periodic->cron changes and release changes into different commits?

PRs readying Goose for a release may include minor laundry-changes like typos and missed-out refactorings (ex: 0.2 PR, 0.3 PR) . @alishamohanty Can we leave the renaming changes as part of this PR as they span only 3 files and ~10 diff items?

@olttwa
Copy link
Member Author

olttwa commented Oct 4, 2024

Can you separate the periodic->cron changes and release changes into different commits?

Split renaming and release-prep changes into 2 separate commits.

@olttwa olttwa merged commit 656fea9 into main Oct 4, 2024
2 checks passed
@olttwa olttwa deleted the prepare-0.6.0-release branch October 4, 2024 11:23
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.

2 participants