sandbox best practices

[mtuchi]

Description
Based on the recent discussion, here are the suggested best practices for using sandboxes:

• Treat Sandboxes as GitHub Branches: Each sandbox should ideally be treated as a GitHub branch. For every new feature or GitHub issue, you should create a dedicated sandbox.
• Establish Connections: Every sandbox needs to be explicitly connected to a specific GitHub branch. When working on a feature, do not work directly on the main branch; instead, create a feature-specific branch and ensure the sandbox is synced to it.
• Manage Pull Requests: Create pull requests from the feature-specific branch to the main branch. This approach makes it easier for reviewers to provide feedback on specific changes rather than dealing with the overwhelming diffs that arise from working on the main branch.
• Handle Dependencies: If you have work that depends on previous changes (e.g., if a sandbox needs to live for a longer period), you can consider creating a "sandbox of a sandbox." This allows you to manage dependent changes without having them all merged into the main branch prematurely.
• Maintain Workflow Discipline: The team is moving toward formalizing this process. Please ensure you are not working directly on the main branch, as this complicates code review and pull request creation.