-
Notifications
You must be signed in to change notification settings - Fork 9
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
Nexus Setup should use up to date NexuShell #245
Labels
0 - _Triaging
New tickets that need to be hashed out a bit more before they hit the backlog.
Enhancement
Enhancements are things that are improvements or features.
Comments
JPRuskin
added
the
Enhancement
Enhancements are things that are improvements or features.
label
Apr 18, 2024
ryanrichter94
added
0 - _Triaging
New tickets that need to be hashed out a bit more before they hit the backlog.
labels
Jun 28, 2024
JPRuskin
added a commit
that referenced
this issue
Sep 18, 2024
This is good practice for work going forward, and begins to enable some of the later stage work we want to do to unify our environment setup(s).
JPRuskin
added a commit
that referenced
this issue
Sep 18, 2024
This is good practice for work going forward, and begins to enable some of the later stage work we want to do to unify our environment setup(s).
JPRuskin
added a commit
that referenced
this issue
Sep 18, 2024
This is good practice for work going forward, and begins to enable some of the later stage work we want to do to unify our environment setup(s).
JPRuskin
added a commit
to JPRuskin/choco-quickstart-scripts
that referenced
this issue
Sep 24, 2024
This is good practice for work going forward, and begins to enable some of the later stage work we want to do to unify our environment setup(s).
JPRuskin
added a commit
that referenced
this issue
Sep 24, 2024
This is good practice for work going forward, and begins to enable some of the later stage work we want to do to unify our environment setup(s).
JPRuskin
added a commit
that referenced
this issue
Sep 27, 2024
This is good practice for work going forward, and begins to enable some of the later stage work we want to do to unify our environment setup(s).
JPRuskin
added a commit
that referenced
this issue
Sep 27, 2024
This is good practice for work going forward, and begins to enable some of the later stage work we want to do to unify our environment setup(s).
JPRuskin
added a commit
that referenced
this issue
Sep 27, 2024
This is good practice for work going forward, and begins to enable some of the later stage work we want to do to unify our environment setup(s). sq
JPRuskin
added a commit
that referenced
this issue
Sep 30, 2024
This is good practice for work going forward, and begins to enable some of the later stage work we want to do to unify our environment setup(s). sq
JPRuskin
added a commit
that referenced
this issue
Sep 30, 2024
This is good practice for work going forward, and begins to enable some of the later stage work we want to do to unify our environment setup(s). sq
ryanrichter94
pushed a commit
that referenced
this issue
Oct 10, 2024
This is good practice for work going forward, and begins to enable some of the later stage work we want to do to unify our environment setup(s). sq
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
0 - _Triaging
New tickets that need to be hashed out a bit more before they hit the backlog.
Enhancement
Enhancements are things that are improvements or features.
Checklist
Is Your Feature Request Related To A Problem? Please describe.
We have multiple functions in use that have diverged slightly from their counterparts in the NexuShell module.
Describe The Solution. Why is it needed?
We should install and use the NexuShell module.
Additional Context
No response
Related Issues
No response
The text was updated successfully, but these errors were encountered: