You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 29, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+59Lines changed: 59 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,3 +51,62 @@ This project aims to provide tools and methodologies for identifying and address
51
51
```
52
52
53
53
9. Run the analysis
54
+
55
+
## Development Guidelines
56
+
57
+
### Branching Strategy
58
+
59
+
-**For Tool development**: branch from and merge into the `tool` branch
60
+
-**For Plugin development**: branch from and merge into the `plugin` branch
61
+
- Use descriptive branch names, e.g., `feature/fehmi-tool-new-detector` or `bugfix/name-plugin-ui-crash`
62
+
63
+
### Commit Messages
64
+
65
+
Follow the [Conventional Commits](https://www.conventionalcommits.org/) specification to aid in automatic changelog generation and versioning.
66
+
67
+
### Pull Requests
68
+
69
+
1. Create a Pull Request (PR) when your feature or fix is ready for review
70
+
2. Ensure all tests pass and code meets the project's quality standards
71
+
3. Request reviews from team members
72
+
73
+
## CI/CD Pipeline
74
+
75
+
GitHub Actions will automatically run on your PR, checking build status, tests, and generating coverage reports. Review the CI/CD output in your PR before merging. The workflows are defined in `.github/workflows/`.
76
+
77
+
### Tool CI Workflow
78
+
79
+
- Triggered on pushes and PRs to the `tool` branch
80
+
- Builds the project, runs tests, and generates a coverage report
81
+
- Creates a release with changelog on merge to `tool`
82
+
83
+
### Plugin CI Workflow
84
+
85
+
- Triggered on pushes and PRs to the `plugin` branch
86
+
- Builds the plugin, runs tests, and generates a coverage report
87
+
- Creates a release with changelog on merge to `plugin`
88
+
89
+
90
+
### Coverage Reports
91
+
92
+
Coverage reports are generated as artifacts in GitHub Actions. Test cases and execution of test cases can be seen here too. To view a coverage report:
0 commit comments