This repository was archived by the owner on Aug 28, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 67
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #506 from Esri/dev
Prepare repo for May 2017 release
- Loading branch information
Showing
427 changed files
with
10,129 additions
and
12,364 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,32 @@ | ||
| <!--- Provide a general summary of the issue in the Title above --> | ||
|
|
||
| ## Expected Behavior | ||
| <!--- If you're describing a bug, tell us what should happen --> | ||
| <!--- If you're suggesting a change/improvement, tell us how it should work --> | ||
|
|
||
| ## Current Behavior | ||
| <!--- If describing a bug, tell us what happens instead of the expected behavior --> | ||
| <!--- If suggesting a change/improvement, explain the difference from current behavior --> | ||
|
|
||
| ## Possible Solution | ||
| <!--- Not obligatory, but suggest a fix/reason for the bug, --> | ||
| <!--- or ideas how to implement the addition or change --> | ||
|
|
||
| ## Steps to Reproduce (for bugs) | ||
| <!--- Provide a link to a live example, or an unambiguous set of steps to --> | ||
| <!--- reproduce this bug. Include code to reproduce, if relevant --> | ||
| 1. | ||
| 2. | ||
| 3. | ||
| 4. | ||
|
|
||
| ## Context | ||
| <!--- How has this issue affected you? What are you trying to accomplish? --> | ||
| <!--- Providing context helps us come up with a solution that is most useful in the real world --> | ||
|
|
||
| ## Your Environment | ||
| <!--- Include as many relevant details about the environment you experienced the bug in --> | ||
| * Version used: | ||
| * Environment name and version (e.g. Chrome 39, node.js 5.4): | ||
| * Operating System and version (desktop or mobile): | ||
| * Link to your project: |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,34 @@ | ||
| <!--- Provide a general summary of your changes in the Title above --> | ||
|
|
||
| ## Description | ||
| <!--- Describe your changes in detail --> | ||
|
|
||
| ## Related Issue | ||
| <!--- This project only accepts pull requests related to open issues --> | ||
| <!--- If suggesting a new feature or change, please discuss it in an issue first --> | ||
| <!--- If fixing a bug, there should be an issue describing it with steps to reproduce --> | ||
| <!--- Please link to the issue here: --> | ||
|
|
||
| ## Motivation and Context | ||
| <!--- Why is this change required? What problem does it solve? --> | ||
|
|
||
| ## How Has This Been Tested? | ||
| <!--- Please describe in detail how you tested your changes. --> | ||
| <!--- Include details of your testing environment, and the tests you ran to --> | ||
| <!--- see how your change affects other areas of the code, etc. --> | ||
|
|
||
| ## Screenshots (if appropriate): | ||
|
|
||
| ## Types of changes | ||
| <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> | ||
| - [ ] Bug fix (non-breaking change which fixes an issue) | ||
| - [ ] New feature (non-breaking change which adds functionality) | ||
| - [ ] Breaking change (fix or feature that would cause existing functionality to change) | ||
|
|
||
| ## Checklist: | ||
| <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> | ||
| <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> | ||
| - [ ] My code follows the code style of this project. | ||
| - [ ] My change requires a change to the documentation. | ||
| - [ ] I have updated the documentation accordingly. | ||
| - [ ] I have read the **CONTRIBUTING** document. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1,54 @@ | ||
| Esri welcomes contributions from anyone and everyone. Please see our [guidelines for contributing](https://github.com/esri/contributing). | ||
| Esri welcomes contributions from anyone and everyone. Please see our [guidelines for contributing](https://github.com/esri/contributing). | ||
|
|
||
| ## How you can contribute code to this repository | ||
|
|
||
| ### Make a new branch in the repo | ||
| Start contributing to the *solutions-geoprocessing-toolbox* repo by making a branch. Make a new branch from **dev** on github.com: | ||
|
|
||
| Select the **dev** drop down | ||
| Type a new branch name. The convention uses your initials and a title separated by dashes "-". For example: *xy-new-suitabilty-tool* | ||
|
|
||
|  | ||
|
|
||
| *Fetch* and *merge* the new branch from the **Esri** remote: [Getting Changes from the repo](#getting-changes-from-the-repo). | ||
|
|
||
| Then checkout your new branch: | ||
|
|
||
| `git checkout <new_branch>` | ||
|
|
||
|
|
||
| ### Getting Changes from the repo | ||
| The solutions-geoprocessing-toolbox repo changes without notice, so make sure you are getting the latest updates often. | ||
|
|
||
| Using git command line check your *remote*: | ||
|
|
||
| `> git remote -v` | ||
|
|
||
| This command should return a list of remotes including: | ||
|
|
||
| `Esri https://github.com/Esri/solutions-geoprocessing-toolbox.git (fetch)` | ||
| `Esri https://github.com/Esri/solutions-geoprocessing-toolbox.git (push)` | ||
|
|
||
| Then *fetch* the changes from the Esri remote: | ||
|
|
||
| `> git fetch Esri` | ||
|
|
||
| And *merge* the changes into the target branch: | ||
|
|
||
| `> git merge Esri/<target branch>` | ||
|
|
||
| This will get your new branch from the repo. | ||
|
|
||
| ### Share Your Mods | ||
| If you've made changes to the repo that you want to share with the community. | ||
|
|
||
| * Commit your changes | ||
| * Sync local with your remote | ||
| * Make a **Pull Request** from your remote fork on github.com  | ||
|
|
||
|
|
||
| ### Notes On Contributing | ||
| * Always work in the **dev** branch, never in *master*. This helps us keep our releases clean. | ||
| * Never merge Pull Requests. The [Repository Owner](#repository-owner) needs to test any updates to make sure the repo is stable. | ||
| * Always log an [Issue](https://github.com/Esri/solutions-geoprocessing-toolbox/issues) for problems you find, though you should check through the existing issues to make sure it wasn't already logged. | ||
|
|
Binary file not shown.
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
Binary file not shown.
Oops, something went wrong.