Add update.yml workflow (and initializing workflow init.yml)

[kenodegard]

Description

Introducing a replacement to the sync.yml workflow. Instead of pushing changes from a centralized location we empower individual repos to pull the files they wish to use (these can even be pulled from any repository, not just conda/infrastructure).

This workflow has been implemented and tested in the conda-sandbox:

• https://github.com/conda-sandbox/upstream (mocks this repo)
• https://github.com/conda-sandbox/downstream (mocks any of the conda org repos, e.g., conda/conda)
• 🤖 Update conda-sandbox/downstream#21 (auto generated PR with templates updates)
• Enable checklist conda-sandbox/downstream#20 (manual PR with manual rendering)

Since the workflow is now a pull process instead of a push process we need to also offer a means of initializing a repository. This is done using the new manually triggered init.yml workflow and allows us to specify where to push the update.yml workflow. The init.yml workflow can also be used to "repair" the update.yml script if ever a broken instance is distributed.

Depends on conda/governance#146
Resolves #678
Resolves #699

[kenodegard]

@jezdez a recent idea I had was to move the primary copy of the short version CODE_OF_CONDUCT.md to https://github.com/conda/governance:

Suggested change

	conda/infrastructure:
	# [required] general files and workflows
	- CODE_OF_CONDUCT.md
	- .github/workflows/cla.yml
	- .github/workflows/update.yml
	conda/governance:
	# [required] community files
	- src: CODE_OF_CONDUCT_SHORT.md
	dst: CODE_OF_CONDUCT.md
	conda/infrastructure:
	# [required] general workflows
	- .github/workflows/cla.yml
	- .github/workflows/update.yml

thoughts?

[jakirkham]

Think we could also create a .github repo for the org and add some of this shared content there

ref: https://github.com/orgs/community/discussions/22144#discussioncomment-3235649

[kenodegard]

We already have https://github.com/conda/.github for the org README.md.

I've been very hesitant to do more with that repo since only some select files are shared with the downstream projects and we sync more than just those files. In some cases we even sync different files to different projects (e.g. not all projects have the same issue templates).

My other concern was the git archives, AFAIK these wont include any of the special files defined in the .github repo so the archives would be an incomplete artifact.

[jezdez]

@jezdez a recent idea I had was to move the primary copy of the short version CODE_OF_CONDUCT.md to conda/governance:

Yeah, now that we have conda/governance, we should use it as the source of truth for governance docs like the CoC, it just didn't exist in the main org when we adopted the CoC.

I hear @jakirkham's point though about having a copy in .github though, it's not a loss to have a copy there as well, but for completeness’s sake, having a copy in every repo doesn't hurt.

[kenodegard]

ah I misunderstood

we already sync files to https://github.com/conda/.github using the old sync workflow (see the workflow and the associated config)

all of the projects using the old sync workflow will be migrated to this new workflow soon