-
Notifications
You must be signed in to change notification settings - Fork 0
/
notes.txt
71 lines (42 loc) · 1.29 KB
/
notes.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
...just some notes for me...
App Accesss
-----------
https://rebrand.ly/utec-tools
Run the App
-----------
streamlit run login.py
pip
---
# install package xyz
pip install xyz
# update package xyz to latest version
pip install xyz -U
Virtual Environments and Requirements
-------------------------------------
# Create a virtual environment:
python -m venv .venv
# Activate virtual environment
.venv\Scripts\activate
# upgrading pip:
py -m pip install --upgrade pip
# install everything from requirements.txt:
pip install -r requirements.txt
Create requirements.txt:
------------------------
pip install pipreqs
pipreqs --force --ignore .venv ./
Git
---
"rebase"
z.B. um eine Branch auf den aktuellen Stand des Masters zu bringen
master: commit_m1 → commit_m2 → commit_m3 → ...
↓ ↓ rebase bringt Änderungen von m2 und m3 in branch
branch: → commit_b1 → commit_b2 → commit_b3 ...
GitHub
------
To close a GitHub issue, you can use any of the following keywords in the commit message, followed by '#' and the number of the issue:
- Close / Closes / Closed
- Fix / Fixes / Fixed
- Resolve / Resolves / Resolved
Example commit message to close issue number 7:
> "new way of importing files - closes #7"