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.

Sign up for GitHub

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

Jump to bottom

chore(very_good_core): v0.7.2 #166

Merged
merged 1 commit into from
Jul 30, 2024
Merged

chore(very_good_core): v0.7.2 #166

merged 1 commit into from
Jul 30, 2024

Conversation

alestiago
Copy link
Contributor

@alestiago alestiago commented Jul 30, 2024 •
edited
Loading

Description

Related to https://github.com/VeryGoodOpenSource/_very_good_chores/issues/127

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore

@alestiago alestiago requested a review from a team as a code owner July 30, 2024 11:29
@alestiago alestiago added chore Changes that don't modify source code or tests product: very_good_core Changes that affect the Very Good Core template. labels Jul 30, 2024
@alestiago alestiago self-assigned this Jul 30, 2024
@alestiago alestiago added this pull request to the merge queue Jul 30, 2024
Merged via the queue into main with commit 1a0affa Jul 30, 2024
5 checks passed
@alestiago alestiago deleted the chore/very_good_core-v0.7.2 branch July 30, 2024 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@tomarra tomarra tomarra approved these changes

Assignees

@alestiago alestiago

Labels
chore Changes that don't modify source code or tests product: very_good_core Changes that affect the Very Good Core template.
Projects
VGV Open Source 🦄 🧙🌟
Archived in project
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@alestiago @tomarra