Yicong-Huang opened a new issue, #3933: URL: https://github.com/apache/texera/issues/3933
This issue tracks a comprehensive round of CI (Continuous Integration) refactoring and alignment with ASF’s official configuration practices. Currently, our required checks for protecting the `main` branch are manually set up from the initial repository donation stage. These checks were inherited from ASF’s default configuration, and we currently lack the ability to modify or manage them properly. To gain full control and ensure consistent CI behavior, we need to migrate to ASF’s declarative configuration approach. Here is the [documentation of configuring `.asf.yaml`](https://github.com/apache/infrastructure-asfyaml). According to the warning in this documentation > [!WARNING] > The names of the required checks are not validated. > > If you modify the `contexts` and `checks` setting for the default branch, consider testing it on a **non** default > branch first. > A typo in these settings for the default branch will prevent you from modifying the `.asf.yaml` file itself. We will need to be careful in this change, and if we get blocked, we need to send a ticket to INFRA to get it fixed. ⸻ Objectives 1. Declare Required Checks in .asf.yaml Explicitly define all required CI checks in the .asf.yaml file, following ASF’s recommended format. 2. Rename and Modernize Check Names Some existing CI job names (e.g., gui, core) are outdated or misaligned with the current project structure. These should be renamed to reflect the updated module layout. 3. Enable Conditional / Optional Checks Introduce the ability to skip or include certain CI jobs based on branch labels or PR metadata. For example, non-critical checks could be marked as optional for documentation-only or frontend-only changes. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
