Skip to content

Latest commit

 

History

History
41 lines (29 loc) · 1.76 KB

File metadata and controls

41 lines (29 loc) · 1.76 KB

Contributing

Thanks for being interested in contributing to DigitalServerHost!

Member Requirements

As an Enterprise-focused organization, we require all core contributors and members to:

  • Use a verified custom domain email (e.g., @digitalserverhost.com).
  • Enable Two-Factor Authentication (2FA) on their GitHub account.
  • Commit Signing: Core members may be required to sign commits via GPG or other verified means to ensure provenance.

Branching Strategy

To maintain a clean and stable codebase, we follow a branch-based workflow:

  • main: The primary branch. It is protected and should always contain production-ready, stable code.
  • Feature Branches: All new features, bug fixes, or documentation updates should be developed in a dedicated feature branch.
  • Branch Naming: Use descriptive names for branches, prefixed by the type of work:
    • feature/your-feature-name
    • bugfix/issue-description
    • chore/cleanup-task
    • docs/update-guidelines

How to Contribute

  1. Fork the repository to your own GitHub account.
  2. Clone the project to your machine.

    [!TIP] Core members and those following GitHub best practices should preferably clone to: ~/github.com/DigitalServerHost/

  3. Create a Branch for your changes. Use a descriptive name as outlined in the Branching Strategy section.
  4. Commit changes to your newly created branch.
  5. Push your work back up to your fork.
  6. Submit a Pull Request so that we can review your changes.

NOTE: Ensure your local main is up-to-date with "upstream" before creating your feature branch!

Code Style

Please ensure your code follows the style of the existing project. For support, contact support@digitalserverhost.com.