Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Device Inventory Playbook #13

Closed
jon-nfc opened this issue Aug 6, 2024 · 4 comments
Closed

Add Device Inventory Playbook #13

jon-nfc opened this issue Aug 6, 2024 · 4 comments
Assignees
Labels
type::feature type for Issues and Merge Requests. Can also be used in discussion in comments and commits
Milestone

Comments

@jon-nfc
Copy link
Member

jon-nfc commented Aug 6, 2024

migrate internal device inventory playbook to this collection.

MR !1 will need to be completed first

Links / References

migrated from https://gitlab.com/nofusscomputing/projects/ansible/collections/centurion_erp_collection/-/issues/1

@jon-nfc
Copy link
Member Author

jon-nfc commented Aug 6, 2024

@jasonpagetas, assign yourself to this issue when you accept the invitation

@jon-nfc jon-nfc added this to the v1.0.0 milestone Aug 12, 2024
@jon-nfc jon-nfc moved this to Ready to Commence in Centurion ERP Aug 12, 2024
@jasonpagetas jasonpagetas self-assigned this Aug 14, 2024
@jasonpagetas
Copy link
Collaborator

As with #14 which branch of this repo do I fork?

@jon-nfc
Copy link
Member Author

jon-nfc commented Aug 14, 2024

As with #14 which branch of this repo do I fork?

The repository is forked, work is generally done on a separate feature branch within your fork and merged back to the development branch of this repo.

Work for both #13 and #14 can be done within the same PR if you prefer.

@jon-nfc jon-nfc added the type::feature type for Issues and Merge Requests. Can also be used in discussion in comments and commits label Aug 14, 2024
@jon-nfc
Copy link
Member Author

jon-nfc commented Aug 14, 2024

I'll merge #16 so that the checks are part of your PR and you can commence work without issues popping up later. #15 will remain blocking for your PR's merge, until I complete it.

You will need to rebase your fork to the updated (post merge) of #16.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type::feature type for Issues and Merge Requests. Can also be used in discussion in comments and commits
Projects
Archived in project
Development

No branches or pull requests

2 participants