docs: Developer: must develop/test in main repo#653
docs: Developer: must develop/test in main repo#653grahamwhaley wants to merge 1 commit intocontainers:masterfrom
Conversation
documentation/Developers.md
Outdated
|
|
||
| **Note:** As `virtcontainers` contains and references its own | ||
| [sub packages](https://github.com/containers/virtcontainers/tree/master/pkg), | ||
| it will **not** build or past its tests in your user fork repo (as the |
documentation/Developers.md
Outdated
|
|
||
| In order to develop and submit PRs for `virtcontainers`, the easist method is to: | ||
|
|
||
| - create a user fork on github. |
There was a problem hiding this comment.
I'd capitalise the first words in all these bullets.
documentation/Developers.md
Outdated
|
|
||
| ``` | ||
| # make check | ||
| # CI=true make check |
There was a problem hiding this comment.
Could you change all the prompts to "$ " as "# " reads as "OMG we're running as root dude!" to me ;)
documentation/Developers.md
Outdated
| [pkg references](https://github.com/containers/virtcontainers/blob/master/cni.go#L25) | ||
| will still reference the main repo, and this results in golang type clashes etc.). | ||
|
|
||
| In order to develop and submit PRs for `virtcontainers`, the easist method is to: |
documentation/Developers.md
Outdated
|
|
||
| In order to develop and submit PRs for `virtcontainers`, the easist method is to: | ||
|
|
||
| - create a user fork on github. |
You cannot build and test in a repo fork, as the sub-pkg references do not move with the fork, and we fail due to type difference failures. Add details on how to add your user fork as a remote to the main repo so you can develop/PR. Also update details on installing required components into /tmp, and the inherent weakness of that. Note you need 'CI=true' to usefully run `make check`. Fixes: containers#642 Signed-off-by: Graham whaley <graham.whaley@intel.com>
bf1ac20 to
c3b142d
Compare
|
@jodh-intel - updated, pushed. |
|
The only potential issue is the lgtm |
| In order to develop and submit PRs for `virtcontainers`, the easiest method is to: | ||
|
|
||
| - Create a user fork on github. | ||
| - Clone the main repo to your development machine (with `go get`) |
There was a problem hiding this comment.
well, it was not an explicit $ got get -d -u <blah> instruction (similarly, did not call out how to clone repos or add remotes). So, nah, I think not.
|
|
||
| # Cloning and Submitting | ||
|
|
||
| If you are just builiding `virtcontainers`, then you can simply clone the main repository |
| from https://github.com/containers/virtcontainers. | ||
|
|
||
| If you wish to develop `virtcontainers`, you should fork the project on github under your | ||
| user. |
There was a problem hiding this comment.
under your user account maybe?
|
@grahamwhaley Need to be closed and moved to https://github.com/kata-containers/runtime/virtcontainers |
You cannot build and test in a repo fork, as the sub-pkg
references do not move with the fork, and we fail due to
type difference failures.
Add details on how to add your user fork as a remote to the
main repo so you can develop/PR.
Also update details on installing required components into
/tmp, and the inherent weakness of that.
Note you need 'CI=true' to usefully run
make check.Fixes: #642
Signed-off-by: Graham whaley graham.whaley@intel.com