chrisjay commited on
Commit
6edabfe
1 Parent(s): c3fd70a

reverted to correct README

Browse files
Files changed (1) hide show
  1. README.md +7 -190
README.md CHANGED
@@ -1,190 +1,7 @@
1
- # Git Large File Storage
2
-
3
- ![CI status][1]
4
-
5
- [1]: https://github.com/git-lfs/git-lfs/workflows/CI/badge.svg
6
-
7
- [Git LFS](https://git-lfs.github.com) is a command line extension and
8
- [specification](docs/spec.md) for managing large files with Git.
9
-
10
- The client is written in Go, with pre-compiled binaries available for Mac,
11
- Windows, Linux, and FreeBSD. Check out the [website](http://git-lfs.github.com)
12
- for an overview of features.
13
-
14
- ## Getting Started
15
-
16
- ### Downloading
17
-
18
- You can install the Git LFS client in several different ways, depending on your
19
- setup and preferences.
20
-
21
- * **Linux users**. Debian and RPM packages are available from
22
- [PackageCloud](https://packagecloud.io/github/git-lfs/install).
23
- * **macOS users**. [Homebrew](https://brew.sh) bottles are distributed, and can
24
- be installed via `brew install git-lfs`.
25
- * **Windows users**. Git LFS is included in the distribution of
26
- [Git for Windows](https://gitforwindows.org/). Alternatively, you can
27
- install a recent version of Git LFS from the [Chocolatey](https://chocolatey.org/) package manager.
28
- * **Binary packages**. In addition, [binary packages](https://github.com/git-lfs/git-lfs/releases) are
29
- available for Linux, macOS, Windows, and FreeBSD.
30
- * **Building from source**. [This repository](https://github.com/git-lfs/git-lfs.git) can also be
31
- built from source using the latest version of [Go](https://golang.org), and the
32
- available instructions in our
33
- [Wiki](https://github.com/git-lfs/git-lfs/wiki/Installation#source).
34
-
35
- ### Installing
36
-
37
- #### From binary
38
-
39
- The [binary packages](https://github.com/git-lfs/git-lfs/releases) include a script which will:
40
-
41
- - Install Git LFS binaries onto the system `$PATH`
42
- - Run `git lfs install` to
43
- perform required global configuration changes.
44
-
45
- ```ShellSession
46
- $ ./install.sh
47
- ```
48
-
49
- #### From source
50
-
51
- - Place the `git-lfs` binary on your system’s executable `$PATH` or equivalent.
52
- - Git LFS requires global configuration changes once per-machine. This can be done by
53
- running:
54
-
55
- ```ShellSession
56
- $ git lfs install
57
- ```
58
-
59
- ## Example Usage
60
-
61
- To begin using Git LFS within a Git repository that is not already configured
62
- for Git LFS, you can indicate which files you would like Git LFS to manage.
63
- This can be done by running the following _from within a Git repository_:
64
-
65
- ```bash
66
- $ git lfs track "*.psd"
67
- ```
68
-
69
- (Where `*.psd` is the pattern of filenames that you wish to track. You can read
70
- more about this pattern syntax
71
- [here](https://git-scm.com/docs/gitattributes)).
72
-
73
- > *Note:* the quotation marks surrounding the pattern are important to
74
- > prevent the glob pattern from being expanded by the shell.
75
-
76
- After any invocation of `git-lfs-track(1)` or `git-lfs-untrack(1)`, you _must
77
- commit changes to your `.gitattributes` file_. This can be done by running:
78
-
79
- ```bash
80
- $ git add .gitattributes
81
- $ git commit -m "track *.psd files using Git LFS"
82
- ```
83
-
84
- You can now interact with your Git repository as usual, and Git LFS will take
85
- care of managing your large files. For example, changing a file named `my.psd`
86
- (tracked above via `*.psd`):
87
-
88
- ```bash
89
- $ git add my.psd
90
- $ git commit -m "add psd"
91
- ```
92
-
93
- > _Tip:_ if you have large files already in your repository's history, `git lfs
94
- > track` will _not_ track them retroactively. To migrate existing large files
95
- > in your history to use Git LFS, use `git lfs migrate`. For example:
96
- >
97
- > ```
98
- > $ git lfs migrate import --include="*.psd"
99
- > ```
100
- >
101
- > For more information, read [`git-lfs-migrate(1)`](https://github.com/git-lfs/git-lfs/blob/master/docs/man/git-lfs-migrate.1.ronn).
102
-
103
- You can confirm that Git LFS is managing your PSD file:
104
-
105
- ```bash
106
- $ git lfs ls-files
107
- 3c2f7aedfb * my.psd
108
- ```
109
-
110
- Once you've made your commits, push your files to the Git remote:
111
-
112
- ```bash
113
- $ git push origin master
114
- Uploading LFS objects: 100% (1/1), 810 B, 1.2 KB/s
115
- # ...
116
- To https://github.com/git-lfs/git-lfs-test
117
- 67fcf6a..47b2002 master -> master
118
- ```
119
-
120
- Note: Git LFS requires at least Git 1.8.2 on Linux or 1.8.5 on macOS.
121
-
122
- ## Limitations
123
-
124
- Git LFS maintains a list of currently known limitations, which you can find and
125
- edit [here](https://github.com/git-lfs/git-lfs/wiki/Limitations).
126
-
127
- ## Need Help?
128
-
129
- You can get help on specific commands directly:
130
-
131
- ```bash
132
- $ git lfs help <subcommand>
133
- ```
134
-
135
- The [official documentation](docs) has command references and specifications for
136
- the tool.
137
-
138
- You can always [open an issue](https://github.com/git-lfs/git-lfs/issues), and
139
- one of the Core Team members will respond to you. Please be sure to include:
140
-
141
- 1. The output of `git lfs env`, which displays helpful information about your
142
- Git repository useful in debugging.
143
- 2. Any failed commands re-run with `GIT_TRACE=1` in the environment, which
144
- displays additional information pertaining to why a command crashed.
145
-
146
- ## Contributing
147
-
148
- See [CONTRIBUTING.md](CONTRIBUTING.md) for info on working on Git LFS and
149
- sending patches. Related projects are listed on the [Implementations wiki
150
- page](https://github.com/git-lfs/git-lfs/wiki/Implementations).
151
-
152
- ## Core Team
153
-
154
- These are the humans that form the Git LFS core team, which runs the project.
155
-
156
- In alphabetical order:
157
-
158
- | [@bk2204][bk2204-user] | [@larsxschneider][larsxschneider-user] | [@PastelMobileSuit][PastelMobileSuit-user] |
159
- |---|---|---|
160
- | [![][bk2204-img]][bk2204-user] | [![][larsxschneider-img]][larsxschneider-user] | [![][PastelMobileSuit-img]][PastelMobileSuit-user] |
161
-
162
- [bk2204-img]: https://avatars1.githubusercontent.com/u/497054?s=100&v=4
163
- [larsxschneider-img]: https://avatars1.githubusercontent.com/u/477434?s=100&v=4
164
- [PastelMobileSuit-img]: https://avatars2.githubusercontent.com/u/37254014?s=100&v=4
165
- [bk2204-user]: https://github.com/bk2204
166
- [larsxschneider-user]: https://github.com/larsxschneider
167
- [PastelMobileSuit-user]: https://github.com/PastelMobileSuit
168
-
169
- ### Alumni
170
-
171
- These are the humans that have in the past formed the Git LFS core team, or
172
- have otherwise contributed a significant amount to the project. Git LFS would
173
- not be possible without them.
174
-
175
- In alphabetical order:
176
-
177
- | [@andyneff][andyneff-user] | [@rubyist][rubyist-user] | [@sinbad][sinbad-user] | [@technoweenie][technoweenie-user] | [@ttaylorr][ttaylorr-user] |
178
- |---|---|---|---|---|
179
- | [![][andyneff-img]][andyneff-user] | [![][rubyist-img]][rubyist-user] | [![][sinbad-img]][sinbad-user] | [![][technoweenie-img]][technoweenie-user] | [![][ttaylorr-img]][ttaylorr-user] |
180
-
181
- [andyneff-img]: https://avatars1.githubusercontent.com/u/7596961?v=3&s=100
182
- [rubyist-img]: https://avatars1.githubusercontent.com/u/143?v=3&s=100
183
- [sinbad-img]: https://avatars1.githubusercontent.com/u/142735?v=3&s=100
184
- [technoweenie-img]: https://avatars3.githubusercontent.com/u/21?v=3&s=100
185
- [ttaylorr-img]: https://avatars2.githubusercontent.com/u/443245?s=100&v=4
186
- [andyneff-user]: https://github.com/andyneff
187
- [sinbad-user]: https://github.com/sinbad
188
- [rubyist-user]: https://github.com/rubyist
189
- [technoweenie-user]: https://github.com/technoweenie
190
- [ttaylorr-user]: https://github.com/ttaylorr
 
1
+ colorFrom: gray
2
+ colorTo: indigo
3
+ sdk: gradio
4
+ sdk_version: 3.0.20
5
+ app_file: app.py
6
+ pinned: false
7
+ ---