Skip to content

Conversation

@graemeniedermayer
Copy link
Contributor

@graemeniedermayer graemeniedermayer commented Jul 25, 2023

This doesn't really solve api documentation at all.

@semjonsona
Copy link
Collaborator

semjonsona commented Jul 26, 2023

Git tip: squashing commits + force push is acceptable in all branches, except when a branch is depended on by the users (main) or a more than a couple of developers. Use this to avoid commits that just fix things in previous commits. Squashing can be replaced with "Amend commit".

@graemeniedermayer graemeniedermayer force-pushed the next branch 3 times, most recently from 9819026 to e12909f Compare July 26, 2023 08:18
@semjonsona
Copy link
Collaborator

The branch with the changes is outdated. You will need to rebase it for the merge to work as expected.

By the way, could you please testdrive thygate:next? I am preparing for the v0.4.3 release.

@semjonsona semjonsona force-pushed the next branch 5 times, most recently from 950633e to 02e38d3 Compare July 28, 2023 15:26
@graemeniedermayer graemeniedermayer force-pushed the next branch 2 times, most recently from e12909f to 2d9812a Compare July 29, 2023 03:44
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