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

doc: Update peer command help to add packageFiles argument #4989

Closed
wants to merge 0 commits into from

Conversation

jmmunoz-kolokium
Copy link
Contributor

Type of change

  • Documentation update

Description

The help information for peer command is missing the package file parameter which should come after the word "install"

Additional details

Fix help information "peer lifecycle chaincode install [flags]" with "peer lifecycle chaincode install [packageFiles] [flags]"

Related issues

Missing argument in help information for command "peer lifecycle chaincode install

Copy link
Contributor

@satota2 satota2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jmmunoz-kolokium
Thank you for submitting the PR. Could you please confirm the following two comments?

Comment 1

  • When updating the peer command reference, there's a slightly special procedure to follow. You need to update fabric/internal/peer/lifecycle/chaincode/install.go as well, following the steps outlined in the documentation.

Here is a concrete example of the steps to follow:

  1. Update the relevant line in fabric/internal/peer/lifecycle/chaincode/install.go.
  2. Build the peer binary with the following commands (make sure to delete the existing peer binary in build/bin if it exists before rebuilding).
    $ cd fabric
    $ make peer
    Building build/bin/peer...
    $./build/bin/peer lifecycle chaincode install --help
  3. Update the command reference (on the documentation side) by running:
    $ make help-docs

Comment 2

Instead of merging from your feature branch (jmmunoz-kolokiumupdate-peer-command-help) into the forked GitHub repository’s main branch and then submitting a PR to the original Fabric repository, you should submit the PR directly from the jmmunoz-kolokiumupdate-peer-command-help branch to the original Fabric repository.

For proper procedures on opening a PR, please refer to:
https://hyperledger-fabric.readthedocs.io/en/latest/github/github.html#opening-a-pull-request-in-github

@jmmunoz-kolokium
Copy link
Contributor Author

jmmunoz-kolokium commented Oct 7, 2024

Hi @satota2 , thanks again for your help.

I have read carefully your instruction and the official guides and I hope I have fullfilled the PR accordingly.

#5011

Best regards

@satota2
Copy link
Contributor

satota2 commented Oct 7, 2024

@jmmunoz-kolokium Thank you for your update. I'll review the new PR.

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.

2 participants