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

Bizarre/docs #1

Merged
merged 3 commits into from
Jan 10, 2023
Merged

Bizarre/docs #1

merged 3 commits into from
Jan 10, 2023

Conversation

bizarre
Copy link
Member

@bizarre bizarre commented Jan 10, 2023

No description provided.

@bizarre bizarre force-pushed the bizarre/docs branch 28 times, most recently from 5bef9a6 to 71fdc7c Compare January 10, 2023 15:58
@bizarre bizarre force-pushed the bizarre/docs branch 5 times, most recently from a26b9f9 to d6cac9a Compare January 10, 2023 16:26
@tsanga tsanga deleted a comment from github-actions bot Jan 10, 2023
@bizarre bizarre force-pushed the bizarre/docs branch 2 times, most recently from d4c1714 to 225242a Compare January 10, 2023 16:29
@tsanga tsanga deleted a comment from github-actions bot Jan 10, 2023
@github-actions
Copy link

github-actions bot commented Jan 10, 2023

Semantic versioning check failed.

Source code have been modified in either musty/src or musty-proc-macro/src but the respective crate version has not been changed.

Please update the version semantically and push the changes.
You can use cargo bump to do this pretty easily (install with cargo install cargo-bump).

master bizarre/docs Source modified
musty@0.1.0 musty@0.0.0 1
musty-proc-macro@0.1.0 musty-proc-macro@0.0.0 1

Semantic Versioning

@bizarre bizarre force-pushed the bizarre/docs branch 2 times, most recently from 97f2704 to 6b37461 Compare January 10, 2023 16:38
@bizarre bizarre merged commit e943a07 into master Jan 10, 2023
@bizarre bizarre deleted the bizarre/docs branch January 16, 2023 11:31
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.

1 participant