Development Considerations and Caveats
以下を希望される場合：
- コードの貢献を提出する
- バグの報告または修正
- 機能や改善の提案
- ドキュメントへの貢献
これらのページの英語版のガイドラインに従ってください。
このページの英語版にアクセスしてください。
This guide helps contributors navigate common development challenges and avoid potential pitfalls when working on GitLab CE and EE.
Consider database and token formatting changes
All deployed code should be designed to support rollbacks, as they are often the fastest way to mitigate incidents. Engineer On Call (EOC) or Incident Manager On Call (IMOC) teams likely do not have full visibility into rollback impacts, so assume any deployment could be reversed.
In addition to following the database migration guide for reversibility, pay special attention to data format changes that affect user-stored data.
When modifying formats for user-stored data (such as authentication tokens, configuration files, or cached values), consider using a phased deployment approach:
- Phase 1: Deploy validation logic that accepts both old and new formats
- Phase 2: Deploy issuance logic that creates data in the new format
This approach ensures:
- Older self-managed instances have backward compatibility support
- New format data is only created after validation logic is deployed
- Rollbacks won’t create validation failures for newly-issued data
- Users experience no disruption during format transitions