Software Engineer workflow
- Approved engineers download the sanitized source archive from Engineering. Production credentials, database backups and deployment/signing keys are not included.
- Edit offline and submit a unified diff with a clear title and test notes. The submission is inert text; the site never applies or executes it. Engineers can see their own proposals. Patches are limited to 60,000 bytes, the form to 80,000 encoded bytes, and the queue to 30 entries / 2,200,000 serialized bytes. Unicode is preserved. If a new submission exceeds storage, it is rejected without changing existing proposals; shorten it or ask the owner to archive reviewed requests privately.
- A full administrator reviews the proposal and requests changes or accepts it for isolated testing. Apply reviewed changes in the development workspace, run the full gate and deploy through the owner-controlled uploader. Approval alone is not a deployment.
Open feature · All guides