Make repo public and clean backups #6
Open
opened 2022-01-22 09:08:24 +00:00 by jon_nfc
·
27 comments
No Branch/Tag Specified
Labels
Clear labels
Bug
Used in discussion about a bug in comments or commits
CVE-2023-5764
Denotes items related to the CVE
CodeReview
Used in comments (issues/MR/commits) to denote code review related items
Documentation
Documentation items
Feature
Used in discussion about a Feature in comments or commits
Lint
Used in comments (issues/MR/commits) to denote lint tasks todo, done, fixed
Privacy
Used in comments (issues/MR/commits) to denote privacy related items
Security
Used in comments (issues/MR/commits) to denote Security related items
breaking-change
label used to denote that the issue/Merge Request does/will introduce a breaking change
bug::reproducable
Given to an issue when the bug has been confirmed as re-producable. Can also be used in comments and commits.
bug::unable to reproduce
Given to an issue when the bug that is not able to be reproduced. Can also be used in comments and commits.
code review::complete
code review::not started
code review::rejected
code review::underway
difficulty::Full Development
Level 3. Difficulty representing that the task to complete must be planned and created.
difficulty::Good First Issue
Level 1. Difficulty representing that the task is very simple and with limited knowledge can be completed.
difficulty::Prior Knowledge
Level 2. Difficulty representing that the task requires some prior knowledge of either the technology or the project for task completion.
documentation::complete
Issues, Merge Requests
documentation::no change required
Issues, Merge Requests and used to denote no documentation changes required
documentation::not started
Issues, Merge Requests
documentation::stalled
Issues, Merge Requests
documentation::underway
Issues, Merge Requests
impact::0
impact::1
impact::2
impact::3
impact::4
impact::5
ops::ansible-roles
OPS project tag
ops::automation
ops::gitlab-ci
OPS project tag
ops::marcas
OPS project tag
ops::python-gitlab-management
OPS project tag
ops::website
priority::0
priority::1
priority::2
priority::3
priority::4
priority::5
stage::Ready for Development
stage::develop
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stage::feedback required
stage::planning
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stage::test
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stale
Label given to issues/merge requests that are considered stale due to no collaboration and is a mark for closure.
triage
Tag given to issues/merge requests requiring triaging by the team.
triage::not_confidential
This tag is given by the triage bot so that URLs can be added to an issue/comment. A triage policy for NFC wide should remove this label.
type::CI / CD
type::automation
This type is used to denote an automation job
type::bug
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::compliance
type::discussion
Type for Issues. Can also be used in discussion in comments.
type::documentation
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::feature
type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::invalid
label given to tickets that require no action or are deem as invalid.
type::quality assurance
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::question
Type for Issues. Can also be used in discussion in comments.
type::security
Type for Issues and Merge Requests.
type::specification
Design specification
workflow::complete
Issues, Merge Requests
workflow::not ready
workflow::not ready::blocked
workflow::not started
Issues, Merge Requests
workflow::ready to commence
Issues, Merge Requests
workflow::stalled
Label given to issues/merge requests where no work has occured in x days iaw triage policy.
workflow::underway
Issues, Merge Requests
workflow::underway::develop
Area/CI-CD
Documentation changes
Area/Documentation
Documentation changes
Area/Security
This is security issue
Area/Testing
Issue or pull request related to testing
Bug
Failure to Confirm
Bug exists due to not confirming/testing code
Bug
Regression
THe bug is a regression of a feature
Bug
To be Confirmed
This bug is not confirmed
Bug
Unable to Reproduce
A developer can not re-create/re-produce the bug
Compat/Breaking
Breaking change that won't be backward compatible
Impact
Critical
1
The impact is critical in that it is blocking or prevents usage.
Impact
High
2
The impact requires that changes be made for continuted usage.
Impact
Low
4
The impact requires the user approach from a different angle for continued usage.
Impact
Medium
3
The impact requires a workaround for continued usage.
Impact
Very Low
5
The impact has a slight effect on usage.
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Priority
Very High
1
The priority is critical
Priority
Very Low
5
The priority is very low
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Type
Bug
Something is not working
Type
Epic
Epic User Story
Type
Feature
Feature / Module
Type
Incident
Something occured related to a service
Type
RFE
Request for Enhancement
Type
Task
A work item that must be done
Urgency
Low
4
Prioritize this amoungst your list of things to do.
Urgency
Major
1
Urgency is so high it should have been dealt with last week.
Urgency
Medium
3
Start as soon as possible.
Urgency
Very High
2
Urgency is high enough to warrant near immediate commencement.
Urgency
Very Low
5
Add this to your list of things to do.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Total Time Spent: 10 minutes
Due Date
jon
10 minutes
No due date set.
Dependencies
No dependencies set.
Reference: nofusscomputing/website#6
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
No description provided.
Delete Branch "%!s()"
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?
📚 Summary
Open up the repo so it's public.
To do so the old website backups need to be moved to a new repo
website-pre-2022
. This repo can contain the full backups of the pre migrated website. They must be encrypted.To do so the following needs to happen.
All of the history before adding the new website structure needs to be moved to the backup repo.
the custom modules blog and tags needs to be placed in it's own project.
Workflow for this repo and to migrate the changes:
Create a new branch from commit (the new data)
Confirm none of the old git history is included
Push the master and dev to the new repo
Delete the master and dev branches
Create an empty master branch
Create a new empty development branch
Merge the clean branch into development
Force push new master and dev branches to this repo
Merge development into master (should already be a MR open.
🔗 References
current wiki added to repo in commit 6c99f01ef4e4293e03293b52be3f290d3fc1f957
new clean repo from b58a76134c8ad8da778756ad1c7e052aa057feb0
new archive repo have all history after 6c99f01ef4e4293e03293b52be3f290d3fc1f957 (the new site) removed
using rebase
✅ Tasks
test works if not figure out a new workflow
new repo created https://gitlab.com/nofusscomputing/infrastructure/website-pre-2022
customizations that have to be moved
blog has been made it's own project
the tags plugin made into its own project
found a licence that is open but for non commercial use
mark issues as confidential that referenced any of the commits to be removed
if repository cleanup does not remove git commits that no longer exist from merge requests, delete the merge requests
marked this issue as related to nofusscomputing/ops#41
changed the description
changed the description
changed the description
changed the description
changed the description
changed the description
changed the description
changed the description
added 15m of time spent
assigned to @jon_nfc
changed the description
added 10m of time spent
ran command
git branch new-mkdocs-website b58a76134c8ad8da778756ad1c7e052aa057feb0
in jon_nfc/website.ran command
git branch old-website 6c99f01ef4e4293e03293b52be3f290d3fc1f957
all branches pushed
wrong commands above
this wont work need to use
git checkout --orphan
deleted branch
new-mkdocs-website
command should be
git checkout --orphan new-mkdocs-website b58a76134c8ad8da778756ad1c7e052aa057feb0
git commit -m "chore: sanitized repo"
un-tested
git merge new-mkdocs-wrbsite
merge dev into branch
new-mkdocs-website
push the master and dev branches to the new website-backup repo
git branch -D development
git branch -D master
git checkout --orphan master
git checkout --orphan development
git merge new-mkdocs-website
git log
to check history and confirm clean.added 15m of time spent
marked the checklist item new repo created as completed
new repo at link https://gitlab.com/nofusscomputing/infrastructure/website-pre-2022
changed the description
mentioned in issue nofusscomputing/ops#41
this thread didn't work
Cleaned git history
below are the commands used to clean the repo
added 1h 45m of time spent
marked the checklist item if repository cleanup does not remove git commits that no longer exist from merge requests, delete the merge requests as completed
mentioned in issue nofusscomputing/ops#55
changed time estimate to 10h
mentioned in issue nofusscomputing/ops#69