-
Notifications
You must be signed in to change notification settings - Fork 909
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
[Docs] Quick flow of steps for first-time developers to Kedro #256
Labels
Issue: Feature Request
New feature or improvement to existing feature
Comments
neomatrix369
added
the
Issue: Feature Request
New feature or improvement to existing feature
label
Feb 26, 2020
neomatrix369
added a commit
to neomatrix369/kedro
that referenced
this issue
Feb 26, 2020
…flow Related to issue kedro-org#256
6 tasks
Closing as PR is merged now! |
neomatrix369
added a commit
to neomatrix369/kedro
that referenced
this issue
Feb 28, 2020
…elated to issue kedro-org#256. Added new release notes entry for PR kedro-org#268, related to issue kedro-org#265
neomatrix369
added a commit
to neomatrix369/kedro
that referenced
this issue
Feb 28, 2020
…elated to issue kedro-org#256. Added new release notes entry for PR kedro-org#268, related to issue kedro-org#265 [skip ci]
neomatrix369
added a commit
to neomatrix369/kedro
that referenced
this issue
Feb 28, 2020
…elated to issue kedro-org#256. [skip ci]
6 tasks
neomatrix369
added a commit
to neomatrix369/kedro
that referenced
this issue
Mar 2, 2020
…elated to issue kedro-org#256. Added new release notes entry for PR kedro-org#268, related to issue kedro-org#265 [skip ci]
neomatrix369
added a commit
to neomatrix369/kedro
that referenced
this issue
Mar 2, 2020
…elated to issue kedro-org#256. [skip ci]
neomatrix369
added a commit
to neomatrix369/kedro
that referenced
this issue
Mar 9, 2020
…elated to issue kedro-org#256. [skip ci]
neomatrix369
added a commit
to neomatrix369/kedro
that referenced
this issue
Mar 9, 2020
…elated to issue kedro-org#256. Added new release notes entry for PR kedro-org#268, related to issue kedro-org#265 [skip ci]
limdauto
added a commit
that referenced
this issue
Mar 10, 2020
… issue #256. [skip ci] (#270) Co-authored-by: Lim H <[email protected]>
neomatrix369
added a commit
to neomatrix369/kedro
that referenced
this issue
Mar 10, 2020
…elated to issue kedro-org#256. Added new release notes entry for PR kedro-org#268, related to issue kedro-org#265 [skip ci]
neomatrix369
added a commit
to neomatrix369/kedro
that referenced
this issue
Mar 15, 2020
…elated to issue kedro-org#256. Added new release notes entry for PR kedro-org#268, related to issue kedro-org#265 [skip ci]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
For both first-time developers or seasoned developers it would be good to have some defined workflow under a section in the CONTRIBUTING.md file.
Context
I couldn't find the first things to do to make sure I can build
kedro
and also next steps in the workflow once we are familiar withkedro
.For e.g. have a look at https://kedro.readthedocs.io/en/stable/02_getting_started/01_prerequisites.html, then run these commands the first-time:
and then onwards always run these:
Before pushing the branch and creating the pull request to the repo.
Possible Implementation
Amend the docs, add links or resources that already exists on the README page. It's highly likely these things already exist but they might be spread across different places in the repo or in the ReadTheDocs page(s).
Possible Alternatives
Ask
kedro
experts at a face-to-face session or raise an issue on githubThe text was updated successfully, but these errors were encountered: