Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 6 Pull Requests 3 Actions Packages Projects Releases Wiki Activity

feat(config): add v1-to-v2 profiles.json migration helper (#105) #123

Open
jcwalker3 wants to merge 1 commits from feat/issue-105-profiles-migration into master
pull from: feat/issue-105-profiles-migration
merge into: Scaled-Tech-Consulting:master
Conversation 0 Commits 1 Files Changed 2
+421
jcwalker3 commented 2026-07-03 03:24:54 -05:00
Owner
Copy Link
Copy Source

Closes #105

Add a migration helper script migrate_profiles.py to convert version 1 profiles.json to version 2 environments shape, preserving keychain references and creating aliases for backwards compatibility. Includes full unit test coverage.

Closes #105 Add a migration helper script migrate_profiles.py to convert version 1 profiles.json to version 2 environments shape, preserving keychain references and creating aliases for backwards compatibility. Includes full unit test coverage.
jcwalker3 added 1 commit 2026-07-03 03:24:54 -05:00
feat(config): add v1-to-v2 profiles.json migration helper (#105) cd633e2c2b
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feat/issue-105-profiles-migration:feat/issue-105-profiles-migration
git checkout feat/issue-105-profiles-migration
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
architecture
Architecture / structural design
 bug
chore
design
Design / investigation, no implementation
 documentation
Docs / runbooks
 enhancement
New feature or improvement
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 mcp
MCP server / tooling
 mutating
Mutating action; requires gating
 nice-to-have
portability
Cross-platform / portability
 read-only
Read-only, no mutation
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 roadmap
Roadmap / umbrella issue
 security
Security / trust boundary
 status:in-progress
Issue is being worked on
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 workflow
Cross-tool workflow
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#123
Delete Branch "feat/issue-105-profiles-migration"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?