-
Notifications
You must be signed in to change notification settings - Fork 210
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
Move contributor documentation to CONTRIBUTING.md #7381
base: master
Are you sure you want to change the base?
Conversation
CONTRIBUTING.md
Outdated
|
||
## Source Code Edit Workflow | ||
Once you've set up the repo, you can move on to making changes to the source code by following the steps below: | ||
1. At the root of the repo, run `git checkout -b "<your-branch-name>"`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know this is very obvious, but suggesting just to be consistent in always explicitly listing what a command is doing.
1. At the root of the repo, run `git checkout -b "<your-branch-name>"`. | |
1. Create your own branch by running `git checkout -b "<your-branch-name>"`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
technically dont need to run this command at the root, you could theoretically run this in any sub dir
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe we should define branch naming policies to help more easily review contirbutions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
okay, I added a new sub section on branch naming policies
CONTRIBUTING.md
Outdated
|
||
## Source Code Edit Workflow | ||
Once you've set up the repo, you can move on to making changes to the source code by following the steps below: | ||
1. At the root of the repo, run `git checkout -b "<your-branch-name>"`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
technically dont need to run this command at the root, you could theoretically run this in any sub dir
|
||
- This is a [sample](https://www.itwinjs.org/sandboxes/iTwinPlatform/3d%20Viewer) of an iTwin viewer - a frontend application that displays infrastructure projects on browsers. It uses many of the APIs and libraries published from this repository. | ||
- You can also look at [other samples](https://developer.bentley.com/samples/) which showcases the capabilities of iTwin.js, and the iTwin Platform. | ||
## Prerequisites |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thoughts on collapsible blocks?
https://gist.github.com/pierrejoubert73/902cc94d79424356a8d20be2b382e1ab
|
||
- This is a [sample](https://www.itwinjs.org/sandboxes/iTwinPlatform/3d%20Viewer) of an iTwin viewer - a frontend application that displays infrastructure projects on browsers. It uses many of the APIs and libraries published from this repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thoughts on hiding the code, and just showing the viewer?
go to the ellipses > embed sandbox > mess around with the option & copy the iframe url
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
our users will still be developers - it'll be nice to show them the coding panel - users can play around with the code, and the panel encourages their own discovery. (If the code is outdated, that's a different issue to tackle)
CONTRIBUTING.md
Outdated
|
||
## Source Code Edit Workflow | ||
Once you've set up the repo, you can move on to making changes to the source code by following the steps below: | ||
1. At the root of the repo, run `git checkout -b "<your-branch-name>"`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe we should define branch naming policies to help more easily review contirbutions?
Attempt to improve clarity between our documentation for users, and contributors of our repo.
From our root README.md, move relevant knowledge needed for contributors to the CONTRIBUTING.md, leaving open space to promote our root README to new users.