2.1.14: Adding external runner for doing a one-time full-sync (#604)

* Adding external runner for doing a one-time full-sync

* Updating docs to describe GHA setup process

2.1.14-rc.2

dont add nulls and undefined to results

2.1.14-rc.1

Merge branch 'main-enterprise' into yj-repo-in-many-suborgs

2.1.13: Fix: array comparison breaks if using the environments plugin (#682)

* update comments from #249

I found the logic behind some of what happened here hard to follow and updated the comments to try to make it easier to follow.

* fix environments updating global array

The environments plugin was changing `MergeDeep.NAME_FIELDS`, which is a global object. The reason was to avoid environments being filtered out from the change list if they only have a name field.
However, the environments plugin has it's own overriden sync method, and thus we can simply drop the whole filtering from that method.

Fixes #108

* remove repeating line

This has to be a "typo" from 9a74e05 calling the same assignment twice. Removing to clean up.

2.1.13-rc.3

Full Changelog: 2.1.13-rc.2...2.1.13-rc.3

2.1.13-rc.2: fix code scanning alerts (#669)

* fix alerts

* fix alerts

* fix alerts

* fix alerts

* add tests and simplify Glob

* fix import to lowercase file

* removed debugging code

2.1.12-rc.1

detect conflict even when a single suborg config is changed

2.1.11-rc.2

What's Changed

• fix: add or update fields in the existing environment or rulesets by @luvsaxena1 in #665
• Add Actions workflow to delete old releases by @decyjphr in #667

New Contributors

• @luvsaxena1 made their first contribution in #665

Full Changelog: 2.1.11-rc.1...2.1.11-rc.2

2.1.11: Add Actions workflow to delete old releases (#667)

* Create delete-old-releases.yml

* Update delete-old-releases.yml

* Update delete-old-releases.yml

2.1.11-rc.1: Environments tolerate concise configuration (#649)

* decompose unit tests, patch sync for environments

* remove logging, combine loops as per review comments

* Add NopCommand, log.error, and errors

* Allow concise config for Environments

This commit combines PR [616](https://github.com/github/safe-settings/pull/616) and [646](https://github.com/github/safe-settings/pull/646)

environments.js
Add defensive code to prevent the GitHub API from being called with undefined data.

In the UI, and API an environment can be added with just an name.
  Now, safe-settings permits this as well.
In the UI, and API an environment can be added without variables.
  Now, safe-settings permits this as well.
In the UI, and API an environment can be added without deployment_protection_rules.
  Now, safe-settings permits this as well.

environments.test.js
Add a test case for the scenario when there are zero existing environments
Add a test case for an environment name change
Add a test case inspired by PR 616 which adds 7 new environments with various attributes
Move expect statements out of aftereach() as there is now variability in what is expected across test cases.
  Specifically, when there is no existing environment, that environment should NOT be queried for variables nor deployment_protection_rules

* Update documentation: Environments permissions.

Addresses issue: [Environments do not get provisioned for repositories set to internal or private #623](https://github.com/github/safe-settings/issues/623)

Adds documentation for permissions required for safe-settings when Environments are used

[List Environments](https://docs.github.com/en/rest/deployments/environments?apiVersion=2022-11-28#list-environments) API requires:
```
The fine-grained token must have the following permission set:

"Actions" repository permissions (read)
```

[Create an environment variable](https://docs.github.com/en/rest/actions/variables?apiVersion=2022-11-28#create-an-environment-variable) API requires:
```
The fine-grained token must have the following permission set:

"Variables" repository permissions (write) and "Environments" repository permissions (write)
```

With permissions added, issue 623 was resolved.