Repo rename is not happening as expected
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- devops
Research direction
Start by tracing how Safe Settings handles a repository rename when the repository name and a file name change in the same pull request; the issue names no source files or tests. Check the force_create: false path and how file changes are associated with repository names. Done means the existing repository is renamed instead of treated as a new repository.
Written by the indexing model from the issue text.
Description
If user wants to rename repo, if he update repo name and file name in same PR, safe settings treats it as new repository, do not rename existing repository
If force_create: false, then safe settings just logs info force_create is set to false, skipping repo creation
Safe Settings should track file level changes like file rename as per repo name, and rename existing repository
Error output, if available
NA
Context
Are you using the hosted instance of probot/settings or running your own?
Own Setup
If running your own instance, are you using it with github.com or GitHub Enterprise?
GitHub Enterprise, using self hosted Safe Settings in AKS cluster
Version of probot/settings
Version of GitHub Enterprise
- Dominant language
- JavaScript
- Stars
- 942
- Forks
- 238
- PR merge metrics
- No merged PRs in 30d
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github-community-projects/safe-settings
-
Teams: teams with organization-role access show up as deletionsPossibly taken @TovaBecker claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
github-community-projects/safe-settings#1144 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github-community-projects/safe-settings#1143 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github-community-projects/safe-settings#1135 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
github-community-projects/safe-settings#1134 ·
Maintainers usually reply within 2 days
-
environments: additive_plugins is ignored, undeclared environments are deletedPossibly taken @yaunj claimed this 12 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github-community-projects/safe-settings#1133 ·
Maintainers usually reply within 2 days
All issues in github-community-projects/safe-settings
Similar issues
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Ionaru/easy-markdown-editor#657 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
TMHSDigital/Free-Game-Dev-Assets#320 ·
Maintainers usually reply within 1 day
-
area:webapp bug finding
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Long working directory path draws over the Console pane's buttons when the Console has no other tabsOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 87/100
ossf/wg-best-practices-os-developers#1209 ·
Maintainers usually reply within 1 day