-
Notifications
You must be signed in to change notification settings - Fork 50
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
Update logo #756
Update logo #756
Conversation
Code Coverage Summary
Diff against main
Results for commit: 7c3099d Minimum allowed coverage is ♻️ This comment has been updated with latest results |
my experience in the past is that you can merge it into main, then we pull it into the release branch. though, there will be a conflict with vbump need to resolve. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm Emily! Thanks, it was already submitted, so the logo will be present in the next release and on gitHub.
Closes #749
To merge after release.
@Melkiades I have made PRs to update the logos in
rlistings
andrtables
. Let me know if you would prefer that we merge directly into the release branches instead of main after the releases.