Совет: git blame — кто изменил строку
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- git
- Domain
- documentation
Research direction
Read tips/_template.md for the required format, then check CONTRIBUTING.md for file and Pull Request instructions. Write a Russian tip showing how git blame identifies the last commit and author for each file line, and how to view the same information on GitHub.
Written by the indexing model from the issue text.
Description
Напиши совет про git blame по шаблону tips/_template.md.
Что показать в примере: для каждой строки файла видно, в каком коммите и кем она изменена последней. Добавь, как то же самое посмотреть на сайте GitHub.
Как оформить файл и Pull Request — в CONTRIBUTING.md.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 1
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from GlebKievsky/git-tips
-
good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
GlebKievsky/git-tips#8 ·
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
GlebKievsky/git-tips#6 ·
-
good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
GlebKievsky/git-tips#5 ·
-
good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
GlebKievsky/git-tips#4 ·
-
good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
GlebKievsky/git-tips#3 ·
All issues in GlebKievsky/git-tips
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bluerobotics/Cockpit-docs#48 ·
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
xavxyz/bei-shan-lin-shui#57 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mozilla/standards-positions#1472 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
w3c/json-ld-api#735 ·