ESLint version

HEAD

What problem do you want to solve?

Currently, our main ESLint repository benefits from the automation provided by Renovate for dependency management. However, this practice has not been uniformly adopted across all our repositories. To address this, I propose the creation of a centralized repository within our ESLint organization. This repository will not only contain configurations for Renovate but also other common GitHub Actions workflows.

Advantages of this Approach:

• Unified Workflow Management: By centralizing our GitHub Actions configurations, including Renovate, we can ensure all ESLint projects follow a consistent workflow for automated tasks, thus improving our overall efficiency.

• Reduction in Redundant Efforts: A central repository eliminates the need to duplicate GitHub Actions configurations in each repository. This reduces repetitive work and ensures uniformity across our projects.

• Simplified Updates and Maintenance: Any changes or updates to our automation configurations would need to be made only once, in the central repository. This simplifies the process of maintaining and updating our workflows.

• Extensibility for ESLint Community Projects: This centralized repository can also be made available to projects under the eslint-communityorg, allowing them to benefit from standardized GitHub Actions workflows.

refs:

• Configure Renovate eslint-community/eslint-plugin-n#44
• making a new repo for github action config files #17424

What do you think is the correct solution?

Creation of a Central Repository: Establish a new repository, possibly named eslint-gha-configs, to house our GitHub Actions configurations:

• renovate
• release-please
• add-to-triage
• stale
• codeql

Participation

• I am willing to submit a pull request for this change.

Additional comments

I'm sure Renovate config can be reused in this way, but I'm not sure if others (like release-please) are also feasible. help wanted!🙌