feat: archive Release repo#35
Conversation
|
Thank you for raising a pull request to update the configuration of your GitHub organization. The following conditions need to be fulfilled for auto-merging to be available:
Otterdog commands and optionsYou can trigger otterdog actions by commenting on this PR:
|
|
Please find below the validation of the requested configuration changes: Diff for 7271ee9Project technology.edc[github_id=eclipse-edc]
there have been 20 validation infos, enable verbose output to display them.
! repository[name="Release"] {
! archived = false -> true
! }
Plan: 0 to add, 1 to change, 0 to delete. |
|
This Pull Request is eligible for auto-merging as it passed the following checks:
Tip In order to automatically merge and apply the changes, add a comment |
|
/otterdog merge |
|
Warning Only the author of the pull request, a project-lead or a member of the admin teams is allowed to auto-merge it. |
|
/otterdog merge |
|
Note The following changes have been applied successfully: Project technology.edc[github_id=eclipse-edc]
there have been 20 validation infos, enable verbose output to display them.
! repository[name="Release"] {
! archived = false -> true
! }
Applying changes:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100% 0:00:00
Done.
Executed plan: 0 added, 1 changed, 0 deleted. |
What this PR changes/adds
Archive
ReleaserepositoryWhy it does that
We're moving all the release workflows into the
.githubrepository (ref)Further notes
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method
signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
Who will sponsor this feature?
Please @-mention the committer that will sponsor your feature.
Linked Issue(s)
Closes # <-- insert Issue number if one exists
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.