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
* Write a model wrapper which follows the [`Model` API](https://github.com/PAIR-code/lit/wiki/api.md#models)
163
163
* Pass models, datasets, and any additional
164
-
[components](documentation/python_api.md#interpretation-components) to the LIT server
164
+
[components](https://github.com/PAIR-code/lit/wiki/api.md#interpretation-components) to the LIT server
165
165
class
166
166
167
167
For a full walkthrough, see
168
-
[adding models and data](documentation/python_api.md#adding-models-and-data).
168
+
[adding models and data](https://github.com/PAIR-code/lit/wiki/api.md#adding-models-and-data).
169
169
170
170
## Extending LIT with new components
171
171
172
172
LIT is easy to extend with new interpretability components, generators, and
173
-
more, both on the frontend or the backend. See the
174
-
[developer guide](documentation/development.md) to get started.
173
+
more, both on the frontend or the backend. See our
174
+
[documentation](https://github.com/PAIR-code/lit/wiki/index.md) to get started.
175
+
176
+
## Pull Request Process
177
+
178
+
To make code changes to LIT, please work off of the `dev` branch and create
179
+
pull requests against that branch. The `main` branch is for stable releases, and it is expected that the `dev` branch will always be ahead of `main` in terms of commits.
0 commit comments