Add contribution guidelines

[dirkmueller]

No description provided.

[github-actions]

Created a staging project on OBS for Tumbleweed: home:defolos:BCI:Staging:Tumbleweed:Tumbleweed-1286
Changes pushed to branch Tumbleweed-1286 as commit 9cb4f9a36846e288c8d17483cb04ce9d3806a789
Build succeeded ✅

Build Results

Repository images in home:defolos:BCI:Staging:Tumbleweed:Tumbleweed-1286 for x86_64: current state: published
Build results:

package name	status	build log
helm-image	✅ succeeded	live log

Repository images in home:defolos:BCI:Staging:Tumbleweed:Tumbleweed-1286 for aarch64: current state: published
Build results:

package name	status	build log
helm-image	✅ succeeded	live log

Repository containerfile in home:defolos:BCI:Staging:Tumbleweed:Tumbleweed-1286 for x86_64: current state: published
Build results:

package name	status	build log
helm-image	⛔ excluded	live log

Repository containerfile in home:defolos:BCI:Staging:Tumbleweed:Tumbleweed-1286 for aarch64: current state: published
Build results:

package name	status	build log
helm-image	⛔ excluded	live log

Build succeeded ✅

To run BCI-tests against this PR, use the following command:

OS_VERSION=tumbleweed TARGET=custom BASEURL=registry.opensuse.org/home/defolos/bci/staging/tumbleweed/tumbleweed-1286/ tox -- -n auto

The following images can be pulled from the staging project:

• registry.opensuse.org/home/defolos/bci/staging/tumbleweed/tumbleweed-1286/images/opensuse/helm

⚠️⚠️ Project and Branch have been deleted ⚠️⚠️ ⚠️⚠️ Project and Branch have been deleted ⚠️⚠️

[alexandrevicenzi]

There's a branch setting that allows these rules to be specified, including auto-merge.

[github-actions]

Created a staging project on OBS for Tumbleweed: home:defolos:BCI:Staging:Tumbleweed:Tumbleweed-1286
Changes pushed to branch Tumbleweed-1286 as commit 4b60c2977e2c3a165b69f4f7ef90191785764a76

[github-actions]

Created a staging project on OBS for Tumbleweed: home:defolos:BCI:Staging:Tumbleweed:Tumbleweed-1286
Changes pushed to branch Tumbleweed-1286 as commit e85a1dc96a7d3a02fa2ebcaedb05a900f9c7fb43
Build succeeded ✅

Build Results

Repository images in home:defolos:BCI:Staging:Tumbleweed:Tumbleweed-1286 for x86_64: current state: published
Build results:

package name	status	build log
helm-image	✅ succeeded	live log

Repository images in home:defolos:BCI:Staging:Tumbleweed:Tumbleweed-1286 for aarch64: current state: published
Build results:

package name	status	build log
helm-image	✅ succeeded	live log

Repository containerfile in home:defolos:BCI:Staging:Tumbleweed:Tumbleweed-1286 for x86_64: current state: published
Build results:

package name	status	build log
helm-image	⛔ excluded	live log

Repository containerfile in home:defolos:BCI:Staging:Tumbleweed:Tumbleweed-1286 for aarch64: current state: published
Build results:

package name	status	build log
helm-image	⛔ excluded	live log

Build succeeded ✅

To run BCI-tests against this PR, use the following command:

OS_VERSION=tumbleweed TARGET=custom BASEURL=registry.opensuse.org/home/defolos/bci/staging/tumbleweed/tumbleweed-1286/ tox -- -n auto

The following images can be pulled from the staging project:

• registry.opensuse.org/home/defolos/bci/staging/tumbleweed/tumbleweed-1286/images/opensuse/helm

⚠️⚠️ Project and Branch have been deleted ⚠️⚠️

[dirkmueller]

There's a branch setting that allows these rules to be specified, including auto-merge.

some of the settings can be configured. but the point here is not to have an implementation (implementation can follow the policy) but a written policy that we can tune the implementation then for, once the alignment is around that.

[dcermak]

Thank you for calling me out personally, but I don't think that mentioning my name improves this document in any way

Suggested change

	* A pull request is considered mergeable if it has no outstanding change
	requests, at least one approval by the maintainers and sufficient time has
	passed. Sufficient time means at least one business day, could be two or
	three in case there are multiple people deciding to send in PRs and Dan has a
	busy day.
	* A pull request is considered mergeable if it has no outstanding change
	requests, at least one approval by the maintainers and sufficient time has
	passed. Sufficient time means at least one business day, could be two or
	three in case there are multiple people deciding to send in PRs.