infrastructure/python-gitlab-management
2
0
Fork 0
Code Issues Pull Requests Actions Projects Releases 29 Wiki Activity

Bug 0.1.0 - imports non-relative path #3

New Issue
Closed
opened 2020-06-03 11:07:20 +00:00 by jon_nfc · 28 comments
jon_nfc commented 2020-06-03 11:07:20 +00:00 (Migrated from gitlab.com)
Copy Link

commentary

the class imports are not working so the package crashes.

To Do

  • rename module directory so it's valid no - i.e. gitlab_management
  • fix up imports so that it's the full path gitlab_management.base
  • confirm the module installs and works prior to publishing.
  • change licence to a less restrictive one and one that encourages collaboration.
## commentary the class imports are not working so the package crashes. ## To Do - [x] rename module directory so it's valid no `-` i.e. `gitlab_management` - [x] fix up imports so that it's the full path `gitlab_management.base` - [x] confirm the module installs and works prior to publishing. - [x] change licence to a less restrictive one and one that encourages collaboration.
jon_nfc commented 2020-06-03 12:01:26 +00:00 (Migrated from gitlab.com)
Copy Link

changed the description

changed the description
jon_nfc commented 2020-06-04 05:06:46 +00:00 (Migrated from gitlab.com)
Copy Link

changed the description

changed the description
jon_nfc commented 2020-06-04 05:07:26 +00:00 (Migrated from gitlab.com)
Copy Link

changed title from Bug 0.1.0 - imports relative path to Bug 0.1.0 - imports {+non-+}relative path

changed title from **Bug 0.1.0 - imports relative path** to **Bug 0.1.0 - imports {+non-+}relative path**
jon_nfc commented 2020-06-04 05:07:26 +00:00 (Migrated from gitlab.com)
Copy Link

changed the description

changed the description
jon_nfc commented 2020-06-04 05:07:54 +00:00 (Migrated from gitlab.com)
Copy Link

created merge request !2 to address this issue

created merge request !2 to address this issue
jon_nfc commented 2020-06-04 05:07:55 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in merge request !2

mentioned in merge request !2
jon_nfc commented 2020-06-04 07:08:52 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 21e535a54b

mentioned in commit 21e535a54b556ddd791135d744afb3d6626680d1
jon_nfc commented 2020-06-04 07:08:52 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 9b410ad1c6

mentioned in commit 9b410ad1c64612067147bcc013bcea5079f69616
jon_nfc commented 2020-06-04 07:08:52 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 63c940d7eb

mentioned in commit 63c940d7eb72056c8d26d0e882c1582b95c2bfaa
jon_nfc commented 2020-06-04 07:08:52 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit d2284538ac

mentioned in commit d2284538ac183f796b04dce21b7c03126e63d82e
jon_nfc commented 2020-06-04 07:08:52 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit c189d23935

mentioned in commit c189d239359c7107299626d9f73d2f43e79ff45c
jon_nfc commented 2020-06-04 07:30:38 +00:00 (Migrated from gitlab.com)
Copy Link

marked the checklist item change licence to a less restrictive one and one that encourages collaboration. as completed

marked the checklist item **change licence to a less restrictive one and one that encourages collaboration.** as completed
jon_nfc commented 2020-06-04 07:31:03 +00:00 (Migrated from gitlab.com)
Copy Link

task change licence to a less restrictive one and one that encourages collaboration complete in commit c189d23935

task `change licence to a less restrictive one and one that encourages collaboration` complete in commit c189d239359c7107299626d9f73d2f43e79ff45c
jon_nfc commented 2020-06-04 07:31:23 +00:00 (Migrated from gitlab.com)
Copy Link

marked the checklist item rename module directory so it's valid no - i.e. gitlab_management as completed

marked the checklist item **rename module directory so it's valid no `-` i.e. `gitlab_management`** as completed
jon_nfc commented 2020-06-04 07:31:46 +00:00 (Migrated from gitlab.com)
Copy Link

task rename module directory so it's valid no - i.e. gitlab_management complete in commit 63c940d7eb

task `rename module directory so it's valid no - i.e. gitlab_management` complete in commit 63c940d7eb72056c8d26d0e882c1582b95c2bfaa
jon_nfc commented 2020-06-04 07:32:43 +00:00 (Migrated from gitlab.com)
Copy Link

marked the checklist item fix up imports so that it's the full path gitlab_management.base as completed

marked the checklist item **fix up imports so that it's the full path `gitlab_management.base`** as completed
jon_nfc commented 2020-06-04 07:33:02 +00:00 (Migrated from gitlab.com)
Copy Link

task fix up imports so that it's the full path gitlab_management.base complete in commit 9b410ad1c6

task `fix up imports so that it's the full path gitlab_management.base` complete in commit 9b410ad1c64612067147bcc013bcea5079f69616
jon_nfc commented 2020-06-04 07:33:06 +00:00 (Migrated from gitlab.com)
Copy Link

marked the checklist item confirm the module installs and works prior to publishing. as completed

marked the checklist item **confirm the module installs and works prior to publishing.** as completed
jon_nfc commented 2020-06-04 07:34:19 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 507b5cbee0

mentioned in commit 507b5cbee0c628e62ad48c610100df59f700efe0
jon_nfc commented 2020-06-04 07:35:42 +00:00 (Migrated from gitlab.com)
Copy Link

added 2h of time spent at 2020-06-04

added 2h of time spent at 2020-06-04
jon_nfc commented 2020-06-04 07:51:38 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 2d7d264973

mentioned in commit 2d7d26497336bc866587a247a71a4f04002c1b33
jon_nfc commented 2020-06-04 07:52:58 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 4a17c3b563

mentioned in commit 4a17c3b563b0dd8bdb3981e4bb9e2abfe3cbdb31
jon_nfc commented 2020-06-04 07:57:27 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 032ffa3906

mentioned in commit 032ffa3906057f277b0c3df11fe2d99388a9ebb2
jon_nfc commented 2020-06-04 08:46:24 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 2707d6b06e

mentioned in commit 2707d6b06ed435ec0052aba51849d134f9bf698f
jon_nfc commented 2020-06-04 08:50:42 +00:00 (Migrated from gitlab.com)
Copy Link

closed

closed
jon_nfc commented 2020-06-08 10:37:00 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in merge request !5

mentioned in merge request !5
jon_nfc commented 2020-06-21 04:56:39 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit cdb15ff55a

mentioned in commit cdb15ff55acbe71a13faee72a16dcb5587d088b1
jon_nfc commented 2020-06-21 07:06:56 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 3a6d563579

mentioned in commit 3a6d563579215abfcf2e0ba073a8a94600d82838
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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
bug::reproducable
type::bug
workflow::complete
Milestone
No items
No Milestone Version 1.0.0
Projects
Clear projects
No project
Assignees
Clear assignees
jason jon
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: infrastructure/python-gitlab-management#3
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?