Eclipse Operations
Last updated
Last updated
PASS is an Eclipse Foundation project and benefits from the resources and knowledge that the Eclipse Foundation has to offer. One of those resources is the Eclipse GH repository configuration.
The repository enables the team committers to via a tool called .
These repo / tools gives access to:
Organization settings
Organization webhooks
Repositories and their settings
Branch protection rules
If a setting is not supplied in the eclipse-pass.jsonnet file, it will default to a predefined value. The full set of default values is available in the Eclipse-managed .
Learn more about .
To make changes to the Otterdog configuration in the repository, follow these steps:
Fork the repository into your own GitHub account.
Make changes to the eclipse-pass.jsonnet file.
Push those changes to the upstream repository.
Create a pull request in the .eclipsefdn repository.
An automated workflow will run, displaying the changes to be applied and validating that the configuration is correctly formatted and structured.
Depending on the type of changes one or more Eclipse engineers will review the PR. Additionally, the project lead's approval may also be required based on the nature of the changes.
Contributors of the project must electronically sign appropriate documents in order to become committers. The following are agreements and policies by Eclipse that a committer must read:
ECA is not configured as a required check for merging in pass-documentation, therefore PRs can be merged with a non-committer. In addition, the EDP explicitly states: "you can merge if you know that the user associated with the commit has signed an ECA", therefore if a user with a different GitHub account with a different email address from their Eclipse committer account, is still able to merge PRs with those commits. This applies to GitBot (GitBook GitHub bot), and Eclipse recognizes this account for making commits.