Skip to content

Commit 4b365d4

Browse files
chore: fix commit messages for conventional compliance
This commit fixes one or more commit messages that didn't follow conventional commits format. The original commits have been squashed and their messages updated to comply with the project's standards. Original issues fixed: - Subject line now follows lowercase convention - Type now uses valid conventional commit types Co-Authored-By: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
1 parent 3f87553 commit 4b365d4

2,283 files changed

Lines changed: 192842 additions & 485963 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.github/AUTOMATED_RELEASE_SETUP.md

Lines changed: 0 additions & 325 deletions
This file was deleted.

.github/BRANCH_PROTECTION.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# Branch Protection Guidance for AiDotNet
2+
3+
We recommend enabling branch protection on both `merge-dev2-to-master` (active base) and `master` (release) with these required status checks:
4+
5+
- CI (.NET) / Lint and Format Check
6+
- CI (.NET) / Build
7+
- CI (.NET) / Test (.NET 8.0.x)
8+
- CI (.NET) / Integration Tests
9+
- CI (.NET) / All Checks Passed
10+
- Quality Gates (.NET) / Publish Size Analysis
11+
- Commit Message Lint / commitlint
12+
13+
Also enable:
14+
- Require pull request reviews (e.g., 1–2 approvals)
15+
- Dismiss stale approvals on new commits (optional)
16+
- Require status checks to pass before merging
17+
- Require branches to be up to date before merging
18+
- Require CODEOWNERS review
19+
20+
Note: The exact names shown in GitHub's UI may include the workflow/job prefixes. Use the exact check names shown on a PR when configuring protection rules.
21+

0 commit comments

Comments
 (0)