Fix: update org references after kagenti to rossoctl rename#90
Merged
Conversation
The org rename left stale kagenti references in the org automation workflows. Two are functional breakages, the rest are correctness/ robustness fixes: - add-to-project.yml: project-url pointed at orgs/kagenti/projects/8, which returns 404 (org Project URLs do not follow the org rename). Repoint to orgs/rossoctl/projects/8. Was failing silently because the step is continue-on-error. - self-assign-reusable.yml, pr-verifier-required.yml, stale.yaml: the 'github.repository != kagenti/.github' self-exclusion guards no longer match the renamed repo (now rossoctl/.github), so these jobs had started running inside the template repo itself instead of being skipped. Update the guards to rossoctl/.github. - project.yml, self-assign.yml: repin 'uses: kagenti/.github/...' to rossoctl/.github (works via redirect today, but fragile). - link_checker.yaml: kagenti.github.io Pages host follows the rename to rossoctl.github.io; the old host 404s. - Update comment/notice URLs referencing kagenti/.github. Signed-off-by: Mariusz Sabath <mrsabath@gmail.com>
esnible
approved these changes
Jul 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The org rename (kagenti to rossoctl) left stale references in the org automation workflows. This fixes them.
Functional breakages
add-to-project.ymlpointed athttps://github.com/orgs/kagenti/projects/8, which returns 404 (org Project URLs do not follow the org rename). Repointed toorgs/rossoctl/projects/8. This was failing silently because the step iscontinue-on-error: true, so items simply stopped being added to the board.github.repository != 'kagenti/.github'inself-assign-reusable.yml(x2),pr-verifier-required.yml, andstale.yamlno longer matched the renamed repo (nowrossoctl/.github). The condition became always-true, so these jobs had started running inside the template repo itself instead of being skipped. Updated torossoctl/.github.Robustness / correctness
uses: kagenti/.github/...torossoctl/.github/...inproject.ymlandself-assign.yml(works via GitHub's org redirect today, but breaks permanently if the old org login is reclaimed).link_checker.yaml:kagenti.github.iotorossoctl.github.io(the GitHub Pages host follows the rename; the old host 404s).kagenti/.github.Part of the Kagenti to rossoctl rename CI cleanup.