Core Integrations team automation

This repository acts as a place to put actions automating tasks for the Core Integrations team.

Deployed actions

Reposettings

Upstream: txqueuelen/reposettings

Reposettings reads a YAML file and ensures that repositories match the specified config.

Shared Workflows

All Workflows located under .github/workflows with prefix reusable_ are meant to be used by external repos (mainly ohi).

reusable_trigger_prerelease

Reusable workflow to create a Github pre-release (not to actually build the pre-release packages, which is done by reusable_pre-release). This is used by ohai repos trigger_prerelease workflow

Find real example at: nri-redis

reusable_push_pr

Reusable workflow that combines the standard testing process for pull requests with the testing of package creation.

Find real example at: nri-redis

on_release

Reusable workflow to release. This is used by ohai repos on_release.yaml workflow

Find real example at: nri-redis

Automatic releases block endpoint

This repo exposes a github page from the gh_page branch containing a file automatic_release_enable which is used as a block endpoint. Automatic pre-releases executes a GET request to it and fails if the status response is different than 200.

The block mechanism can be manually set by manually executing the workflow Block automatic releases and unset by the workflow Unblock automatic releases from the Actions panel.

Renovate shared config

renovate-base.json5 defines a base renovate configuration to be used in all core-int repositories.

It can be used directly like this:

{
  "extends": [
    "github>newrelic/coreint-automation:renovate-base.json5"
  ]
}

Or include additional rules if needed:

 "extends": [
   "github>newrelic/coreint-automation:renovate-base.json5"
  ],
  "packageRules": [
    // ...
  ]

Check Shareable Config Presets in Renovate Docs for further information.

Renovate configuration resources

• Renovate logs can be check in mend developer website.

A note about vulnerabilities

As noted in our security policy, New Relic is committed to the privacy and security of our customers and their data. We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals.

If you believe you have found a security vulnerability in this project or any of New Relic's products or websites, we welcome and greatly appreciate you reporting it to New Relic through HackerOne.

If you would like to contribute to this project, review these guidelines.

To all contributors, we thank you! Without your contribution, this project would not be what it is today. We also host a community project page dedicated to Project Name.

Support

New Relic hosts and moderates an online forum where customers can interact with New Relic employees as well as other customers to get help and share best practices. Like all official New Relic open source projects, there's a related Community topic in the New Relic Explorers Hub.

License

[Project Name] is licensed under the Apache 2.0 License.

[If applicable: The [project name] also uses source code from third-party libraries. You can find full details on which libraries are used and the terms under which they are licensed in the third-party notices document.]