You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We love contributions from our community of users! This document explains our guidelines and workflows. Please take care to follow them, as it helps us keep things moving smoothly.
4
+
5
+
#### Environment setup
6
+
7
+
0. Install Node.js (4 or newer) and npm (3 or newer).
8
+
1. Make a fork of Swagger-UI on GitHub, then clone your fork to your machine.
9
+
2. Run `npm install` in your Swagger-UI directory.
10
+
3. Run `npm run dev`. `localhost:3200` should open automatically.
11
+
4. You're ready to go!
12
+
13
+
#### Branching model
14
+
15
+
Feature branches should be prefixed with `ft/`.
16
+
17
+
Bugfix branches should be prefixed with `bug/`.
18
+
19
+
Version branches should be prefixed with `v/`.
20
+
21
+
After the forward slash, include a short description of what you're fixing. For example: `bug/fix-everything-that-was-broken`. For versions, add the version that will be released via the branch, for example: `v/1.2.3`.
22
+
23
+
If there's an issue filed that you're addressing in your branch, include the issue number directly after the forward slash. For example: `bug/1234-fix-all-the-other-things`.
24
+
25
+
#### Filing issues
26
+
27
+
-**Do** include the Swagger-UI build you're using - you can find this by opening your console and checking `window.versions.swaggerUi`
28
+
-**Do** include a spec that demonstrates the issue you're experiencing.
29
+
-**Do** include screenshots, if needed. GIFs are even better!
30
+
-**Do** place code inside of a pre-formatted container by surrounding the code with triple backticks.
31
+
-**Don't** open tickets discussing issues with the Swagger/OpenAPI specification itself, or for issues with projects that use Swagger-UI.
32
+
-**Don't** open an issue without searching the issue tracker for duplicates first.
33
+
34
+
#### Committing
35
+
36
+
- Break your commits into logical atomic units. Well-segmented commits make it _much_ easier for others to step through your changes.
37
+
- Limit your subject (first) line to 50 characters (GitHub truncates more than 70).
38
+
- Provide a body if you'd like to explain your commit in detail.
39
+
- Capitalize the beginning of your subject line, and do not end the subject line with a period.
40
+
- Your subject line should complete this sentence: `If applied, this commit will [your subject line].`
41
+
- Don't use [magic GitHub words](https://help.github.com/articles/closing-issues-using-keywords/) in your commits to close issues - do that in the pull request for your code instead.
42
+
43
+
_Adapted from [How to Write a Git Commit Message](https://chris.beams.io/posts/git-commit/#seven-rules)._
44
+
45
+
#### Making pull requests
46
+
47
+
-**Do** summarize your changes in the PR body. If in doubt, write a bullet-point list titled `This PR does the following:`.
48
+
-**Do** include references to issues that your PR solves, and use [magic GitHub words](https://help.github.com/articles/closing-issues-using-keywords/) to close those issues automatically when your PR is merged.
49
+
-**Do** include tests that cover new or changed functionality.
50
+
-**Do** be careful to follow our ESLint style rules. We recommend installing an ESLint plugin if you use a graphical code editor.
51
+
-**Do** make sure that tests and the linter are passing by running `npm test` locally, otherwise we can't merge your pull request.
52
+
-**Don't** include any changes to files in the `dist/` directory - we update those files only during releases.
53
+
-**Don't** mention maintainers in your original PR body - we probably would've seen it anyway, so it just increases the noise in our inboxes. Do feel free to ping maintainers if a week has passed and you've heard nothing from us.
54
+
-**Don't** open PRs for custom functionality that only serves a small subset of our users - custom functionality should be implemented outside of our codebase, via a plugin.
0 commit comments