feat: request for new repository

[paullatzelsperger]

Description

This PR represents a request for a new repository named identity-trust, the purpose of which will be to host specification documents regarding topics revolving around identity and trust (a.k.a. "SSI")

\cc @jimmarino @wolf4ood @matgnt @dr-markus @borisrizov-zf

I hope the configuration regarding gh-pages is correct, especially the part about the gh_pages_build_type, I merely copied it over from another repo.

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

• [ ] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
• [ ] Copyright and license header are present on all affected files

[github-actions[bot]]

Diff for 973c7c7d9ede09cd0d300d427c43a1a86e9a5a96:

```diff Printing local diff for configuration at '/home/runner/work/.eclipsefdn/.eclipsefdn/otterdog-configs/otterdog.json' Actions are indicated with the following symbols: + create ! modify ! forced update - delete Organization eclipse-tractusx[id=eclipse-tractusx] there have been 39 validation infos, enable verbose output with '-v' to to display them. + add repository[name="identity-trust"] { + allow_auto_merge = false + allow_forking = true + allow_merge_commit = true + allow_rebase_merge = true + allow_squash_merge = true + allow_update_branch = false + archived = false + default_branch = "main" + delete_branch_on_merge = false + dependabot_alerts_enabled = true + dependabot_security_updates_enabled = false + description = null + gh_pages_build_type = "legacy" + gh_pages_source_branch = "gh-pages" + gh_pages_source_path = "/" + has_discussions = true + has_issues = true + has_projects = true + has_wiki = true + homepage = null + is_template = false + merge_commit_message = "PR_TITLE" + merge_commit_title = "MERGE_MESSAGE" + name = "identity-trust" + private = false + secret_scanning = "enabled" + secret_scanning_push_protection = "enabled" + squash_merge_commit_message = "COMMIT_MESSAGES" + squash_merge_commit_title = "COMMIT_OR_PR_TITLE" + template_repository = null + topics = [] + web_commit_signoff_required = false + } + add environment[name="github-pages", repository="identity-trust"] { + branch_policies = [ + "gh-pages" + ], + deployment_branch_policy = "selected" + name = "github-pages" + reviewers = [] + wait_timer = "0" + } Plan: 2 to add, 0 to change, 0 to delete. ``` ```diff Showing diff to a canonical version of the configuration at '/home/runner/work/.eclipsefdn/.eclipsefdn/otterdog-configs/otterdog.json' Organization eclipse-tractusx[id=eclipse-tractusx] ```

[netomi]

LGTM

[netomi]

Is there already a ticket in the sig-infra repo or can someone else approve that?

[paullatzelsperger]

Is there already a ticket in the sig-infra repo or can someone else approve that?

I didn't create one, but can do so. First time for me - could you post the link to the issue page?

[netomi]

https://github.com/eclipse-tractusx/sig-infra/issues

but I dont know how its now done in the tractus-x project. There were talks about a document to highlight how new resources should be provisioned by whom. Maybe in this case just ask for approval from a project lead?

[paullatzelsperger]

https://github.com/eclipse-tractusx/sig-infra/issues

but I dont know how its now done in the tractus-x project. There were talks about a document to highlight how new resources should be provisioned by whom. Maybe in this case just ask for approval from a project lead?

@Siegfriedk is it enough to ask for your +1 here or is something else required?

[Siegfriedk]

Yes the normal documented workflow is creating a ticket in sig-infra as we discovered that most people are not able to properly create a PR lke this.

A highlight from a project lead shoould be enough without a sig-infra ticket

[netomi]

repo has been created.