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
Add Pre-Commit Hooks and Fix Dev Dependency Issues (#12)
* Add pre commit functionality to the repo, fix any errors popping up with current state of main and running the pre commit checks, fix install and versioning issues with dev dependencies
* update DEVELOPING.md docs
If you already have a copy, fetch upstream changes.
97
-
98
-
```bash
99
-
git fetch upstream
100
-
```
101
-
102
-
4. Create a feature branch to work in.
103
-
104
-
```bash
105
-
git checkout -b feature-xxx remotes/upstream/main
106
-
```
107
-
108
-
5. Work in your feature branch.
109
-
110
-
```bash
111
-
git commit -a
112
-
```
113
-
114
-
6. Periodically rebase your changes
115
-
116
-
```bash
117
-
git pull --rebase
118
-
```
119
-
120
-
7. When done, combine ("squash") related commits into a single one
121
-
122
-
```bash
123
-
git rebase -i upstream/main
124
-
```
125
-
126
-
This will open your editor and allow you to re-order commits and merge them:
127
-
- Re-order the lines to change commit order (to the extent possible without creating conflicts)
128
-
- Prefix commits using `s` (squash) or `f` (fixup) to merge extraneous commits.
129
-
130
-
8. Submit a pull-request
131
-
132
-
```bash
133
-
git push origin feature-xxx
134
-
```
135
-
136
-
Go to your fork main page
137
-
138
-
```bash
139
-
https://github.com/<username>/guidellm
140
-
```
141
-
142
-
If you recently pushed your changes GitHub will automatically pop up a `Compare & pull request` button for any branches you recently pushed to. If you click that button it will automatically offer you to submit your pull-request to the `neuralmagic/guidellm` repository.
143
-
144
-
- Give your pull-request a meaningful title.
145
-
You'll know your title is properly formatted once the `Semantic Pull Request` GitHub check
146
-
transitions from a status of "pending" to "passed".
147
-
- In the description, explain your changes and the problem they are solving.
148
-
149
-
9. Addressing code review comments
150
-
151
-
Repeat steps 5. through 7. to address any code review comments and rebase your changes if necessary.
152
-
153
-
Push your updated changes to update the pull request
154
-
155
-
```bash
156
-
git push origin [--force] feature-xxx
157
-
```
158
-
159
-
`--force` may be necessary to overwrite your existing pull request in case your
160
-
commit history was changed when performing the rebase.
161
-
162
-
Note: Be careful when using `--force` since you may lose data if you are not careful.
0 commit comments