4 Commits
Author SHA1 Message Date
brahmi 0d0c3dac4d Merge pull request 'Add CONTRIBUTING.md' (#7) from issue-2-contributing into main
Reviewed-on: #7
Reviewed-by: sakshi <sakwork0507@gmail.com>
2026-10-15 19:49:04 +00:00
sakshi 15f8a00343 Merge pull request 'Add product README' (#8) from issue-1-readme into main
Reviewed-on: #8
Reviewed-by: brahmi <dalvibrahmi@outlook.com>
2026-10-15 19:47:44 +00:00
sakshi ae2628b917 Add product README 2026-10-15 19:40:11 +00:00
brahmi d484ad4a37 Add CONTRIBUTING.md 2026-10-15 19:31:18 +00:00
2 changed files with 27 additions and 2 deletions
+10
View File
@@ -0,0 +1,10 @@
# Contributing to TwinTrack
1. Every change starts as an issue. Pick or create one before you start.
2. Branch from `main` as `issue-<number>-<short-name>`.
3. Open a pull request with `Closes #<number>` in the description.
4. The other team member reviews it, leaves at least one comment or question,
and approves once it is addressed. You cannot approve your own pull request.
5. After approval, merge. The issue closes automatically.
6. `main` is protected: no direct pushes.
7. Never commit passwords, tokens, private keys or personal data.
+17 -2
View File
@@ -1,3 +1,18 @@
# twintrack
# TwinTrack
TwinTrack: Group 1's startup product
A small team task tracker that Group 1 (SSW 590) uses as its startup product.
The same application is delivered by two CI/CD pipelines (GitHub Actions and
Jenkins) so the tools can be compared on security, speed, and operations.
## Status
Planning. See the issues for the current backlog.
## How we work
1. Every change starts as an issue.
2. Branch from `main` as `issue-<number>-<short-name>`.
3. Open a pull request with `Closes #<number>` in the description.
4. The other team member reviews and approves; then merge.
## Team
- Brahmi Dalvi — infrastructure (Gitea, cloud, CI)
- Sakshi Deshpande — product (application, tests, documentation)