Configure refs policies - Githubissues

RaboDeToro-hub-2 / uvlhub

Repository of feature models in UVL format integrated with Zenodo and flamapy following Open Science principles - Developed by DiversoLab

https://docs.uvlhub.io

0 stars 0 forks source link

Configure refs policies #10

Open bloxio3001 opened 1 week ago

bloxio3001 commented 1 week ago

PRs must behave following our policies:

Merge is blocked until approved by one member (at least)
Merge is blocked until tests finish
The main and develop branches must be protected
Tags must only be created on successful releases

EPIC:

1

bloxio3001 commented 6 days ago

Main and Develop

Restrict creations, updates and deletions
Require a pull request before merging
- Required Approvals: 1
- Dismiss stale pull request approvals when new commits are pushed
- Require conversation resolution before merging
- Require status check to pass
- Require branches to be up-to-date before merging
- Check: Conventional Commits
- Check: Pytest
- Check: Lint
- FUTURE STATUS CHECKS TO BE ADDED AFTER IMPLEMEMTING THEM
- Block force pushes
- Require code scanning results (Set to, but not integrated, Codacy at High or Higher FUTURE CODE SCANNING SYSTEM TO BE INTEGRATED)
- Require deployments to succeed (only on main)
- Environment: Development

Tags

Restrict deletions
- Require status check to pass
- Require branches to be up-to-date before merging
- Check: Conventional Commits
- Check: Pytest
- Check: Lint
- FUTURE STATUS CHECKS TO BE ADDED AFTER IMPLEMEMTING THEM
- Block force pushes
- Require deployments to succeed
- Environment: Staging