File .gitignore added (mode: 100644) (index 0000000..20505dc) |
|
1 |
|
# Created by .ignore support plugin (hsz.mobi) |
|
2 |
|
### Node template |
|
3 |
|
# Logs |
|
4 |
|
/logs |
|
5 |
|
*.log |
|
6 |
|
npm-debug.log* |
|
7 |
|
yarn-debug.log* |
|
8 |
|
yarn-error.log* |
|
9 |
|
|
|
10 |
|
# Runtime data |
|
11 |
|
pids |
|
12 |
|
*.pid |
|
13 |
|
*.seed |
|
14 |
|
*.pid.lock |
|
15 |
|
|
|
16 |
|
# Directory for instrumented libs generated by jscoverage/JSCover |
|
17 |
|
lib-cov |
|
18 |
|
|
|
19 |
|
# Coverage directory used by tools like istanbul |
|
20 |
|
coverage |
|
21 |
|
|
|
22 |
|
# nyc test coverage |
|
23 |
|
.nyc_output |
|
24 |
|
|
|
25 |
|
# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files) |
|
26 |
|
.grunt |
|
27 |
|
|
|
28 |
|
# Bower dependency directory (https://bower.io/) |
|
29 |
|
bower_components |
|
30 |
|
|
|
31 |
|
# node-waf configuration |
|
32 |
|
.lock-wscript |
|
33 |
|
|
|
34 |
|
# Compiled binary addons (https://nodejs.org/api/addons.html) |
|
35 |
|
build/Release |
|
36 |
|
|
|
37 |
|
# Dependency directories |
|
38 |
|
node_modules/ |
|
39 |
|
jspm_packages/ |
|
40 |
|
|
|
41 |
|
# TypeScript v1 declaration files |
|
42 |
|
typings/ |
|
43 |
|
|
|
44 |
|
# Optional npm cache directory |
|
45 |
|
.npm |
|
46 |
|
|
|
47 |
|
# Optional eslint cache |
|
48 |
|
.eslintcache |
|
49 |
|
|
|
50 |
|
# Optional REPL history |
|
51 |
|
.node_repl_history |
|
52 |
|
|
|
53 |
|
# Output of 'npm pack' |
|
54 |
|
*.tgz |
|
55 |
|
|
|
56 |
|
# Yarn Integrity file |
|
57 |
|
.yarn-integrity |
|
58 |
|
|
|
59 |
|
# dotenv environment variables file |
|
60 |
|
.env |
|
61 |
|
|
|
62 |
|
# parcel-bundler cache (https://parceljs.org/) |
|
63 |
|
.cache |
|
64 |
|
|
|
65 |
|
# next.js build output |
|
66 |
|
.next |
|
67 |
|
|
|
68 |
|
# nuxt.js build output |
|
69 |
|
.nuxt |
|
70 |
|
|
|
71 |
|
# Nuxt generate |
|
72 |
|
dist |
|
73 |
|
|
|
74 |
|
# vuepress build output |
|
75 |
|
.vuepress/dist |
|
76 |
|
|
|
77 |
|
# Serverless directories |
|
78 |
|
.serverless |
|
79 |
|
|
|
80 |
|
# IDE / Editor |
|
81 |
|
.idea |
|
82 |
|
|
|
83 |
|
# Service worker |
|
84 |
|
sw.* |
|
85 |
|
|
|
86 |
|
# Mac OSX |
|
87 |
|
.DS_Store |
|
88 |
|
|
|
89 |
|
# Vim swap files |
|
90 |
|
*.swp |
File README.md deleted (index 16eff96..0000000) |
1 |
|
**Edit a file, create a new file, and clone from Bitbucket in under 2 minutes** |
|
2 |
|
|
|
3 |
|
When you're done, you can delete the content in this README and update the file with details for others getting started with your repository. |
|
4 |
|
|
|
5 |
|
*We recommend that you open this README in another tab as you perform the tasks below. You can [watch our video](https://youtu.be/0ocf7u76WSo) for a full demo of all the steps in this tutorial. Open the video in a new tab to avoid leaving Bitbucket.* |
|
6 |
|
|
|
7 |
|
--- |
|
8 |
|
|
|
9 |
|
## Edit a file |
|
10 |
|
|
|
11 |
|
You’ll start by editing this README file to learn how to edit a file in Bitbucket. |
|
12 |
|
|
|
13 |
|
1. Click **Source** on the left side. |
|
14 |
|
2. Click the README.md link from the list of files. |
|
15 |
|
3. Click the **Edit** button. |
|
16 |
|
4. Delete the following text: *Delete this line to make a change to the README from Bitbucket.* |
|
17 |
|
5. After making your change, click **Commit** and then **Commit** again in the dialog. The commit page will open and you’ll see the change you just made. |
|
18 |
|
6. Go back to the **Source** page. |
|
19 |
|
|
|
20 |
|
--- |
|
21 |
|
|
|
22 |
|
## Create a file |
|
23 |
|
|
|
24 |
|
Next, you’ll add a new file to this repository. |
|
25 |
|
|
|
26 |
|
1. Click the **New file** button at the top of the **Source** page. |
|
27 |
|
2. Give the file a filename of **contributors.txt**. |
|
28 |
|
3. Enter your name in the empty file space. |
|
29 |
|
4. Click **Commit** and then **Commit** again in the dialog. |
|
30 |
|
5. Go back to the **Source** page. |
|
31 |
|
|
|
32 |
|
Before you move on, go ahead and explore the repository. You've already seen the **Source** page, but check out the **Commits**, **Branches**, and **Settings** pages. |
|
33 |
|
|
|
34 |
|
--- |
|
35 |
|
|
|
36 |
|
## Clone a repository |
|
37 |
|
|
|
38 |
|
Use these steps to clone from SourceTree, our client for using the repository command-line free. Cloning allows you to work on your files locally. If you don't yet have SourceTree, [download and install first](https://www.sourcetreeapp.com/). If you prefer to clone from the command line, see [Clone a repository](https://confluence.atlassian.com/x/4whODQ). |
|
39 |
|
|
|
40 |
|
1. You’ll see the clone button under the **Source** heading. Click that button. |
|
41 |
|
2. Now click **Check out in SourceTree**. You may need to create a SourceTree account or log in. |
|
42 |
|
3. When you see the **Clone New** dialog in SourceTree, update the destination path and name if you’d like to and then click **Clone**. |
|
43 |
|
4. Open the directory you just created to see your repository’s files. |
|
44 |
|
|
|
45 |
|
Now that you're more familiar with your Bitbucket repository, go ahead and add a new file locally. You can [push your change back to Bitbucket with SourceTree](https://confluence.atlassian.com/x/iqyBMg), or you can [add, commit,](https://confluence.atlassian.com/x/8QhODQ) and [push from the command line](https://confluence.atlassian.com/x/NQ0zDQ). |
|