nofusscomputing/website-template
1
0
Fork 0
Code Issues 1 Pull Requests 2 Actions Projects Releases Wiki Activity

chore: release to stable #17

Open
jon_nfc wants to merge 49 commits from development into master
pull from: development
merge into: nofusscomputing:master
Conversation 15 Commits 49 Files Changed 31 +1854
jon_nfc commented 2024-02-02 12:15:01 +00:00 (Migrated from gitlab.com)
Copy Link
No description provided.
jon_nfc commented 2024-02-02 12:15:01 +00:00 (Migrated from gitlab.com)
Copy Link

added 30m of time spent

added 30m of time spent
jon_nfc commented 2024-02-02 12:15:01 +00:00 (Migrated from gitlab.com)
Copy Link

assigned to @jon_nfc

assigned to @jon_nfc
jon_nfc commented 2024-02-02 12:16:46 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 103baa53521d88454ca1a7ac82893853c2654698

mentioned in commit 103baa53521d88454ca1a7ac82893853c2654698
jon_nfc commented 2024-02-02 12:16:47 +00:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

  • 103baa53 - ci: use matric job to update parent repos

Compare with previous version

added 1 commit <ul><li>103baa53 - ci: use matric job to update parent repos</li></ul> [Compare with previous version](/nofusscomputing/infrastructure/website-template/-/merge_requests/14/diffs?diff_id=913236430&start_sha=db172f4594391a18883b24768aae531c8245fce0)
jon_nfc commented 2024-02-02 12:19:23 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 63a7300db9

mentioned in commit 63a7300db9a3f0f4d1214dbfd85641dec447253c
jon_nfc commented 2024-02-02 12:19:25 +00:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

  • 63a7300d - ci: use matrix job to update parent repos

Compare with previous version

added 1 commit <ul><li>63a7300d - ci: use matrix job to update parent repos</li></ul> [Compare with previous version](/nofusscomputing/infrastructure/website-template/-/merge_requests/14/diffs?diff_id=913239149&start_sha=103baa53521d88454ca1a7ac82893853c2654698)
jon_nfc commented 2024-02-02 12:22:50 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit f5cbde1f1d

mentioned in commit f5cbde1f1de7cac9094df8898e3d09eb01d9cd4c
jon_nfc commented 2024-02-02 12:22:51 +00:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

Compare with previous version

added 1 commit <ul><li>f5cbde1f - fix: ci no docs to build</li></ul> [Compare with previous version](/nofusscomputing/infrastructure/website-template/-/merge_requests/14/diffs?diff_id=913243066&start_sha=63a7300db9a3f0f4d1214dbfd85641dec447253c)
jon_nfc commented 2024-02-02 13:09:37 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 2bcc17652b

mentioned in commit 2bcc17652babd4027e7245c6367841e2580ec317
jon_nfc commented 2024-02-02 13:09:39 +00:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

  • 2bcc1765 - ci: add docker-glpi and kube_monitoring

Compare with previous version

added 1 commit <ul><li>2bcc1765 - ci: add docker-glpi and kube_monitoring</li></ul> [Compare with previous version](/nofusscomputing/infrastructure/website-template/-/merge_requests/14/diffs?diff_id=913297641&start_sha=f5cbde1f1de7cac9094df8898e3d09eb01d9cd4c)
jon_nfc commented 2024-02-08 05:30:19 +00:00 (Migrated from gitlab.com)
Copy Link

added 3 commits

  • 28e70fee - feat(template): add itil runbook template
  • 702df2eb - feat(deploy): deploy updated to runbooks repo
  • f5a82d36 - Merge branch 'feat-itil-runbook' into 'development'

Compare with previous version

added 3 commits <ul><li>28e70fee - feat(template): add itil runbook template</li><li>702df2eb - feat(deploy): deploy updated to runbooks repo</li><li>f5a82d36 - Merge branch &#39;feat-itil-runbook&#39; into &#39;development&#39;</li></ul> [Compare with previous version](/nofusscomputing/infrastructure/website-template/-/merge_requests/14/diffs?diff_id=918558118&start_sha=2bcc17652babd4027e7245c6367841e2580ec317)
jon_nfc commented 2024-06-15 14:39:27 +00:00 (Migrated from gitlab.com)
Copy Link

added 2 commits

  • 2f3982eb - refactor(mkdocs): use alternative method for plugins key so merging works
  • 67ca423a - Merge branch 'feat-mkdocstrings' into 'development'

Compare with previous version

added 2 commits <ul><li>2f3982eb - refactor(mkdocs): use alternative method for plugins key so merging works</li><li>67ca423a - Merge branch &#39;feat-mkdocstrings&#39; into &#39;development&#39;</li></ul> [Compare with previous version](/nofusscomputing/infrastructure/website-template/-/merge_requests/14/diffs?diff_id=1038112305&start_sha=f5a82d3604faca56756eec91acee28ff89defd1d)
jon_nfc commented 2024-06-30 17:46:15 +00:00 (Migrated from gitlab.com)
Copy Link

added 2 commits

  • 7b1736d9 - feat: dont expand the navigation menu
  • 92c4b16a - Merge branch 'dont-expand-navigation' into 'development'

Compare with previous version

added 2 commits <ul><li>7b1736d9 - feat: dont expand the navigation menu</li><li>92c4b16a - Merge branch &#39;dont-expand-navigation&#39; into &#39;development&#39;</li></ul> [Compare with previous version](/nofusscomputing/infrastructure/website-template/-/merge_requests/14/diffs?diff_id=1051325658&start_sha=67ca423aaa61fc6f6901459973c12b191abc328d)
jon_nfc commented 2024-06-30 18:01:37 +00:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

  • 8735f623 - feat: add django template publish

Compare with previous version

added 1 commit <ul><li>8735f623 - feat: add django template publish</li></ul> [Compare with previous version](/nofusscomputing/infrastructure/website-template/-/merge_requests/14/diffs?diff_id=1051328592&start_sha=92c4b16a14524e7b5b18171d4e21b72676c36fbf)
jon_nfc commented 2025-05-28 22:39:50 +00:00 (Migrated from gitlab.com)
Copy Link

added 1 commit

  • aed23768 - feat(gitlab_ci): update to current HEAD

Compare with previous version

added 1 commit <ul><li>aed23768 - feat(gitlab_ci): update to current HEAD</li></ul> [Compare with previous version](/nofusscomputing/infrastructure/website-template/-/merge_requests/14/diffs?diff_id=1372886538&start_sha=8735f623dc5e1d9c9e46e50db03b4c41cb3d1efd)
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 development:development
git checkout development
Sign in to join this conversation.
Reviewers
No Reviewers
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
Assignees
Clear assignees
jon
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nofusscomputing/website-template#17
No description provided.
Delete Branch "development"

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?