forked from pouchdb/pouchdb
-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' of https://github.com/pouchdb/pouchdb into upst…
…ream
- Loading branch information
Showing
88 changed files
with
988 additions
and
754 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
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,21 @@ | ||
name: Mark stale issues and pull requests | ||
|
||
on: | ||
schedule: | ||
- cron: "30 1 * * *" | ||
|
||
jobs: | ||
stale: | ||
|
||
runs-on: ubuntu-latest | ||
|
||
steps: | ||
- uses: actions/stale@v1 | ||
with: | ||
repo-token: ${{ secrets.GITHUB_TOKEN }} | ||
stale-issue-label: 'stale' | ||
stale-issue-message: 'This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days' | ||
exempt-issue-labels: 'pinned' | ||
days-before-stale: 60 | ||
days-before-close: 7 | ||
only-labels: 'enhancement, needs reproducing, question' |
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
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 |
---|---|---|
|
@@ -6,30 +6,29 @@ Welcome, so you are thinking about contributing to PouchDB? Awesome, this is a g | |
Get in Touch | ||
------------ | ||
|
||
The following documentation should answer most of the common questions about how to get starting contributing, if you have any questions, please feel free to get in touch @ [Freenode IRC](https://www.irccloud.com/invite?channel=pouchdb&hostname=irc.freenode.net&port=6697&ssl=1), in [the Google Groups mailing list](https://groups.google.com/forum/#!forum/pouchdb), and [on StackOverflow](http://stackoverflow.com/questions/tagged/pouchdb). Or you can [tweet @pouchdb](http://twitter.com/pouchdb). | ||
The following documentation should answer most of the common questions about how to get starting contributing, if you have any questions, please feel free to get in touch @ [the Google Groups mailing list](https://groups.google.com/forum/#!forum/pouchdb), and [on StackOverflow](http://stackoverflow.com/questions/tagged/pouchdb). Or you can [tweet @pouchdb](http://twitter.com/pouchdb). | ||
|
||
Most project discussions should happen on the Mailing list / Bug Tracker and IRC, however if you are a first time contributor and want some help getting started feel free to send a private email to any of the following maintainers: | ||
Most project discussions should happen on the Mailing list / Bug Tracker, however if you are a first time contributor and want some help getting started feel free to send a private email to any of the following maintainers: | ||
|
||
* Dale Harvey ([email protected], daleharvey on IRC) | ||
* Nolan Lawson ([email protected], nolanlawson on IRC) | ||
* Calvin Metcalf ([email protected], calvinmetcalf on IRC) | ||
* Dale Harvey ([email protected]) | ||
|
||
#### PouchDB meeting | ||
Help Wanted | ||
---------------- | ||
|
||
We hold a weekly 'office hours' meeting on IRC (irc.freenode.net#pouchdb) on Mondays at 5:00PM UTC (9:00 AM Pacific, 12:00 PM Eastern, 10:30 PM IST), this is open to anyone and a time when developers and users discuss issues they are having or working on. | ||
If you are looking for something to work on, we try to maintain a list of issues that should be suitable for first time contributions, they can be found tagged [help-wanted](https://github.com/pouchdb/pouchdb/issues?labels=help-wanted&state=open). | ||
|
||
Help Wanted | ||
Triage | ||
---------------- | ||
|
||
If you are looking for something to work on, we try to maintain a list of issues that should be suitable for first time contributions, they can be found tagged [help wanted](https://github.com/pouchdb/pouchdb/issues?labels=help%20wanted&state=open). | ||
Bugs that get filed have no labels [and are triaged](https://github.com/pouchdb/pouchdb/issues?q=is%3Aissue+is%3Aopen+no%3Alabel). A bug should be given one of the following labels: bug, enhancement, needs-reproducing, question during triage. Issues with the `bug` label will not be marked stale. | ||
|
||
|
||
Guide to Contributions | ||
-------------------------------------- | ||
|
||
* Almost all Pull Requests for features or bug fixes will need tests | ||
* We follow [Felix's Node.js Style Guide](https://github.com/felixge/node-style-guide) | ||
* Almost all Pull Requests for features or bug fixes will need tests (seriously, it's really important) | ||
* Before opening a pull request run `$ npm test` to lint test the changes and run node tests. Preferably run the browser tests as well. | ||
* Commit messages should follow the following style: | ||
|
||
``` | ||
|
@@ -46,11 +45,6 @@ Dependencies | |
PouchDB needs the following to be able to build and test your build, if you haven't installed them then best to do so now, we will wait. | ||
|
||
* [Node.js](http://nodejs.org/) | ||
* [CouchDB](http://couchdb.apache.org/) | ||
|
||
CouchDB must be running and available at `http://localhost:5984`. If you can open that URL in a browser and see `"couchdb": "Welcome"`, then it's working. | ||
|
||
You'll also need to ensure that CORS is enabled on the CouchDB. You can easily do this by running `npm install -g add-cors-to-couchdb` and then `add-cors-to-couchdb`. | ||
|
||
**On Windows?** PouchDB's build and tests work on Windows, but you will have to follow [Microsoft's guidelines for Windows](https://github.com/Microsoft/nodejs-guidelines/blob/master/windows-environment.md#environment-setup-and-configuration) to ensure you can install and compile native add-ons. Also, we recommend [Git Bash for Windows](https://git-scm.com/download/win) because our build relies on many Bash- and Unix-isms. Another option is [Windows Subsystem for Linux](https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux). | ||
|
||
|
@@ -72,40 +66,46 @@ UMD module to `dist/`. All of this logic is in `bin/build.sh`. | |
Testing PouchDB | ||
-------------------------------------- | ||
|
||
Running PouchDB tests is really simple (5 minutes), go to [TESTING](./TESTING.md) for instructions. | ||
|
||
Debugging PouchDB | ||
-------------------------------------- | ||
The main PouchDB test suite can be run with: | ||
|
||
PouchDB uses the `debug` [module](https://www.npmjs.org/package/debug) for debug | ||
logging, to turn on the log output enable the debug flag in node: | ||
$ npm test | ||
|
||
DEBUG=pouchdb:* | ||
If you would like to test against your a CouchDB instance you are currently running you can specify that with `COUCH_HOST`: | ||
|
||
Or in the browser: | ||
$ COUCH_HOST="http://127.0.0.1:5984" npm test | ||
|
||
PouchDB.debug.enable('pouchdb:*'); | ||
There is more information about the various test suites and testing options in [TESTING](./TESTING.md). | ||
|
||
Git Essentials | ||
-------------------------------------- | ||
|
||
Workflows can vary, but here is a very simple workflow for contributing a bug fix: | ||
|
||
$ git clone [email protected]:myfork/pouchdb.git | ||
$ git remote add pouchdb https://github.com/pouchdb/pouchdb.git | ||
|
||
$ git clone https://github.com/pouchdb/pouchdb.git | ||
$ git checkout -b 121-issue-keyword master | ||
# Write tests + code | ||
$ git add src/afile.js | ||
$ git commit -m "(#121) - A brief description of what I changed" | ||
|
||
Once you have some code to push, fork the [PouchDB repository](https://github.com/pouchdb/pouchdb) then push your changes to your fork: | ||
|
||
$ git remote add myfork https://github.com/myfork/pouchdb.git | ||
$ git push origin 121-issue-keyword | ||
|
||
Now when you visit https://github.com/myfork/pouchdb there should be a button that will let you create a pull request. | ||
|
||
Building PouchDB Documentation | ||
-------------------------------------- | ||
|
||
The source for the website http://pouchdb.com is stored inside the `docs` directory of the PouchDB repository, you can make changes and submit pull requests as with any other patch. To build and view the website locally you will need to install [jekyll](http://jekyllrb.com/) and a few other gems. Jekyll is installed using [bundler](http://bundler.io/) so you need to install that first. | ||
The source for the website http://pouchdb.com is stored inside the `docs` directory of the PouchDB repository, you can make changes and submit pull requests as with any other patch. To build and view the website locally you will need to have the Ruby development package installed. | ||
On Ubuntu this is done with: | ||
|
||
$ sudo apt install -y ruby-dev | ||
|
||
You then neet to install [jekyll](http://jekyllrb.com/) and a few other gems. Jekyll is installed using [bundler](http://bundler.io/) so you need to install that first. | ||
On Ubuntu you will need root permissions to do this so prefix the ```gem``` command with ```sudo``` | ||
|
||
$ gem install bundler | ||
$ [sudo] gem install bundler | ||
$ npm run install-jekyll | ||
|
||
If you haven't already done so, you'll also need to run `npm install` to pull in packages for the dev server: | ||
|
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
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
Oops, something went wrong.