在git操作中改为由dev分支rebase到master分支比较好?

Open
#18 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
git
Domain
documentation

Research direction

Read the Git branch maintenance section at git_pr.md#自己的git分支维护 and check the rebase instructions at the end of that article. Determine whether the documented rebase direction should be reversed before submitting a PR; done means the instructions clearly state the correct branch direction.

Written by the indexing model from the issue text.

Description

在文章的结尾,git操作是由master分支rebase到dev分支,之后提交pr。这里是否应该改成由dev分支rebase到master?

Dominant language
C
Stars
60
Forks
48
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from RT-Thread/rtthread-specification

All issues in RT-Thread/rtthread-specification

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.