docker/execution_environment
1
0
Fork 0
Code Issues 6 Pull Requests Actions Projects Releases 39 Wiki Activity

chore: Release 0.17.1 #281

Merged
jon_nfc merged 2 commits from development into master 2024-05-02 01:04:17 +00:00
Conversation 11 Commits 2 Files Changed 1 +3 -1
jon_nfc commented 2024-04-25 18:32:46 +00:00 (Migrated from gitlab.com)
Copy Link

next release

next release
jon_nfc commented 2024-04-26 22:34:10 +00:00 (Migrated from gitlab.com)
Copy Link

ToDo

  • add glpi collection nofusscomputing/projects/ansible/collections/glpi!1
# ToDo - [x] add glpi collection nofusscomputing/projects/ansible/collections/glpi!1
jon_nfc commented 2024-05-02 00:52:35 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit d71ee25c24

mentioned in commit d71ee25c2450567217f529e143723b05ac5cd6e0
jon_nfc commented 2024-05-02 00:52:35 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 5288a657cc

mentioned in commit 5288a657cc43429a5a59ae3cfefca754ba421bbb
jon_nfc commented 2024-05-02 00:52:35 +00:00 (Migrated from gitlab.com)
Copy Link

added 2 commits

  • d71ee25c - fix(collection): add nofusscomputing.glpi
  • 5288a657 - fix(collection): add nofusscomputing.netbox

Compare with previous version

added 2 commits <ul><li>d71ee25c - fix(collection): add nofusscomputing.glpi</li><li>5288a657 - fix(collection): add nofusscomputing.netbox</li></ul> [Compare with previous version](/nofusscomputing/projects/ansible/execution_environment/-/merge_requests/254/diffs?diff_id=997628147&start_sha=7f403ca0ce888c69d6f2d0225e58294272768abf)
jon_nfc commented 2024-05-02 00:53:01 +00:00 (Migrated from gitlab.com)
Copy Link

resolved all threads

resolved all threads
jon_nfc (Migrated from gitlab.com) scheduled this pull request to auto merge when all checks succeed 2024-05-02 00:53:20 +00:00
jon_nfc commented 2024-05-02 00:53:21 +00:00 (Migrated from gitlab.com)
Copy Link

added 10m of time spent

added 10m of time spent
jon_nfc commented 2024-05-02 00:59:22 +00:00 (Migrated from gitlab.com)
Copy Link

assigned to @jon_nfc

assigned to @jon_nfc
jon_nfc commented 2024-05-02 01:04:18 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 7af16b5b5a

mentioned in commit 7af16b5b5a4f543e83e1e10b7739b4836e979ab2
jon_nfc (Migrated from gitlab.com) merged commit 7af16b5b5a into master 2024-05-02 01:04:18 +00:00
jon_nfc commented 2024-05-02 01:25:32 +00:00 (Migrated from gitlab.com)
Copy Link

changed title from chore: Release 0.1{-.....-} to chore: Release 0.1{+7.1+}

changed title from **chore: Release 0.1{-.....-}** to **chore: Release 0.1{+7.1+}**
jon_nfc commented 2024-05-02 01:51:19 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit f64a45d921

mentioned in commit f64a45d921deeb4ffd7858e8cdd91f6f6756165b
jon_nfc commented 2024-05-03 13:17:00 +00:00 (Migrated from gitlab.com)
Copy Link

mentioned in commit 3ba335620c

mentioned in commit 3ba335620cfd878048d0bceeadb45b3b35017012
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
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: docker/execution_environment#281
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?