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
The aim is to improve repo maintenance, documentation and quality. As first good steps I should:
improve contributing guidance explaining which branch should be the target when opening a PR etc. Updates contributing guide #29
refactor the release beta process not to base on automatic numbering as now it is inconsistent with the change log and it is impossible to keep this aligned Updates beta release flow #27
make main a safe branch
make dev safe branch (only PR's allowed with bypass possible for PnP crew)
turn on dependabot
turn on codeQL
make dev default branch (at least until the official release)
## 🎯 Aim
The aim is to refactor the release process not to base on auto generated
numbers in flow. The main reason for that is problem with keeping this
in sync with changelog for beta releases which currently is done
manually and is usually out of sync.
## ✅ What was done
- [X] modified the release .yml
- [X] along the way added small fixes in issue na bug templates
- [X] prepared new release
## 🔗 Related issue
Related: #21
🎯 Aim
The aim is to improve repo maintenance, documentation and quality. As first good steps I should:
The text was updated successfully, but these errors were encountered: