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

Remove references to install command from the tutorial. Fixes #1877 #1928

Merged
merged 1 commit into from
Mar 16, 2023
Merged

Remove references to install command from the tutorial. Fixes #1877 #1928

merged 1 commit into from
Mar 16, 2023

Conversation

ivanperez-keera
Copy link
Member

Originating Project/Creator Ivan Perez (Ames)
Related Issue(s) #1877

Change Description

Remove references to the install command from the tutorial.

Rationale

The tutorial refers to the install command in the 'Build Ref Deployment' section. However, that command was removed in 20b5f29, a commit released as early as v2.0.0~193^2.

Testing/Review Recommendations

Ensure that, as written now, claims about the build command are accurate.

Future Work

None.

The tutorial refers to the "install" command in the 'Build Ref
Deployment' section.  However, that command was removed in 20b5f29, a
commit released as early as v2.0.0~193^2.

This commit removes references to the install command from the tutorial.

The mention that the build command also copies the binaries to the bin
dir is moved earlier in the text, simply because it flows better when
the rest of the note about the install command is removed.
@LeStarch LeStarch changed the base branch from master to devel March 11, 2023 02:57
@LeStarch LeStarch closed this Mar 11, 2023
@LeStarch LeStarch reopened this Mar 11, 2023
@ivanperez-keera
Copy link
Member Author

ivanperez-keera commented Mar 11, 2023

@LeStarch This was reopened. Is everything ok, and should I be filing PRs against devel instead of master?

@thomas-bc
Copy link
Collaborator

@ivanperez-keera thank you for making this PR! PRs should be opened against devel, this was closed and re-opened for the CI to be re-triggered after the rebasing. The CI fails are unrelated, I'm looking into it right now.

@ivanperez-keera
Copy link
Member Author

@thomas-bc Thanks! I'll do that in the future. As I understand it, I don't need to change anything (e.g., rebase the commits in my fork and force-push) but, if I do, please let me know.

@LeStarch
Copy link
Collaborator

@thomas-bc I think you fixed these CI issues. How should we handle PRs like this that failed?

@thomas-bc thomas-bc changed the base branch from devel to master March 16, 2023 19:40
@thomas-bc thomas-bc changed the base branch from master to devel March 16, 2023 19:40
@thomas-bc thomas-bc closed this Mar 16, 2023
@thomas-bc thomas-bc reopened this Mar 16, 2023
@thomas-bc
Copy link
Collaborator

@LeStarch I tweaked with the PR by both rebasing to get the latest devel, then closing/reopening to update the Workflow pointers. We can do the same for #1930 but given the scope of the PR and knowing why the workflow failed, it might not be best practice but I would say it's safe to merge.

@LeStarch LeStarch merged commit e9c2144 into nasa:devel Mar 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants