Skip to content

Revise README: Remove milestones and update branching - #20

Merged
sromic1990 merged 2 commits into
mainfrom
dev
Apr 12, 2026
Merged

sromic1990 merged 2 commits into
mainfrom
dev

Conversation

@sromic1990

Copy link
Copy Markdown
Owner

Removed detailed development milestones and added branching strategy.

Removed detailed development milestones and added branching strategy.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Updates the project README to remove the previously detailed milestone plan and document a dev-based branching workflow for ongoing development.

Changes:

  • Removed the “Development Milestones” section from the README.
  • Updated the branching strategy text to introduce a dev branch and describe a feature-branch workflow via dev.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread README.md
Comment on lines 69 to +72
- **`main`** is always buildable. Never commit directly to it.
- Every **feature on a branch** (`feature/short-description`).
- When a feature is complete: open a Pull Request, review diff, merge.
- **`dev`** is the development branch.
- Every **feature on a branch** (`feature/short-description`) is branched off from dev.
- When a feature is complete: open a Pull Request, review diff, merge to dev, then to main.

Copilot AI Apr 12, 2026

Copy link

Choose a reason for hiding this comment

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

The branching diagram/code block above still shows feature branches coming directly off main, but the bullets now define dev as the integration branch and features branching from dev. Please update the diagram to reflect dev (and the correct branch-off point) so the README is internally consistent.

Copilot uses AI. Check for mistakes.
Comment thread README.md
Comment on lines +78 to 80
- Gives a clean history that someone can actually read later
- The tags mean someone can always `git checkout milestone-1` and have a working app

Copilot AI Apr 12, 2026

Copy link

Choose a reason for hiding this comment

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

The README still instructs tagging and checking out milestone-* (e.g., milestone-1), but the "Development Milestones" section was removed in this PR, so these tags no longer have documented meaning. Either remove/rename the milestone tagging guidance (e.g., to release tags) or reintroduce a brief definition of what each milestone tag represents.

Copilot uses AI. Check for mistakes.
@sromic1990

Copy link
Copy Markdown
Owner Author

@copilot apply changes based on the comments in this thread

…release tags

Agent-Logs-Url: https://github.com/sromic1990/Doculith/sessions/52d76d9e-c0d6-419f-9b50-af40344944de

Co-authored-by: sromic1990 <13477194+sromic1990@users.noreply.github.com>

Copilot AI commented Apr 12, 2026

Copy link
Copy Markdown
Contributor

@copilot apply changes based on the comments in this thread

Applied both fixes in commit 1e7fa56:

  1. Branching diagram — updated to show feature branches coming off dev instead of main, making the diagram consistent with the bullet points.
  2. Milestone tags — replaced milestone-* tag references with semantic version release tags (v1.0.0, v1.1.0, etc.) since the Development Milestones section was removed.

@sromic1990
sromic1990 merged commit c53e7f6 into main Apr 12, 2026
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