Skip to content

docs: align developer guide with java-tron CONTRIBUTING.md#346

Open
abn2357 wants to merge 1 commit into
tronprotocol:masterfrom
abn2357:fix_dev_guide
Open

docs: align developer guide with java-tron CONTRIBUTING.md#346
abn2357 wants to merge 1 commit into
tronprotocol:masterfrom
abn2357:fix_dev_guide

Conversation

@abn2357

@abn2357 abn2357 commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Align docs/developers/java-tron.md with the java-tron source CONTRIBUTING.md.
  • Unify branch naming to release_*, feature/*, hotfix/*; add the hotfix fork-only PR rule, the git rebase tip, and commit scope examples.
  • Restore the PR title casing/period rules; fix the chore type description and remove the nonexistent TIP "In Progress" state.
  • Clarify release_ branch naming and fix the merge target to develop.
  • Fix grammar, Pull Request wording, honorific consistency, and a missing example.

Test plan

  • mkdocs build succeeds
  • Developer guide page renders and internal links resolve

- unify branch naming to release_*, feature/*, hotfix/*
- add hotfix fork-only PR rule, git rebase tip, commit scope examples
- restore PR title casing/period rules
- fix chore type description and drop nonexistent TIP "In Progress" state
- clarify release_ branch naming, fix merge target to develop
- fix grammar, Pull Request wording and honorific consistency
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