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

docs: add contributing, git, and styleguide docs #56

Merged
merged 1 commit into from
May 14, 2024

Conversation

0xdeafbeef
Copy link
Member

No description provided.

@0xdeafbeef 0xdeafbeef force-pushed the 0xdeafbeef/push-yltnpnxmvnpm branch 3 times, most recently from e63565d to 2d21083 Compare May 7, 2024 22:22

- **Fork the Repository:** Fork the repository or create a new branch in the
repository if you have write access. Prefix the branch name with your
username.
Copy link
Member

Choose a reason for hiding this comment

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

is it really necessary to prefix branch with username?

Copy link
Member Author

Choose a reason for hiding this comment

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

For now, it's too much. Later, it will be easier to gc dead branches etc

- **Fork the Repository:** Fork the repository or create a new branch in the
repository if you have write access. Prefix the branch name with your
username.
- **Commit Structure:** We review each commit separately, and we do not use the
Copy link
Member

Choose a reason for hiding this comment

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

nice idea, but not applicable for current development stage

Copy link
Member Author

Choose a reason for hiding this comment

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

If you're at a stage where structuring commits is not feasible, you can always squash them into a single commit before submitting your PR. It will make the life of a reviewer a bit easier

Copy link
Member

Choose a reason for hiding this comment

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

Let's be honest, we do not review every single commit. We review the whole code


## No-Merge Policy

The broxus/tycho repo uses what is known as a "rebase workflow." This means
Copy link
Member

Choose a reason for hiding this comment

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

We discussed previously merges are fine. Did things change?

Copy link
Member Author

Choose a reason for hiding this comment

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

  • create branch
  • make changes
  • if master or upstream branch was updated - rebase on top if it. Don't merge it
  • after review pr will be merged
intial state:

A - B - C  (master)
     \
      D - E  (feature)
     
Rebase onto master:

A - B - C - D' - E'  (master, feature)

Merge master into branch:

A - B - C  (master)
     \       \
      D - E - M  (feature)

@0xdeafbeef 0xdeafbeef force-pushed the 0xdeafbeef/push-yltnpnxmvnpm branch from 2d21083 to a9332fc Compare May 14, 2024 12:46
@0xdeafbeef 0xdeafbeef force-pushed the 0xdeafbeef/push-yltnpnxmvnpm branch from a9332fc to a1af099 Compare May 14, 2024 12:48
@0xdeafbeef 0xdeafbeef merged commit ca18b96 into master May 14, 2024
1 check passed
@Rexagon Rexagon deleted the 0xdeafbeef/push-yltnpnxmvnpm branch May 14, 2024 14:48
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.

3 participants