A live demo where I use git commands along with Travis-CI / GitHub to fix a bug & push a release.

Hit the subscribe button to receive more videos like this!

---

Timestamped Table of Contents:

0:00 -- What we'll cover in this video
0:43 -- The patterns used in this video can be used in any project
1:46 -- Trying to get useful information out of issues that folks open
2:47 -- A fun bug with virtualenv 20.0.3 related to symlinks
5:23 -- Going back 1 level of abstraction really helps to debug errors
7:07 -- Opening issues on related repos that are the cause of your library's bugs
8:00 -- Once you know the problem, the solution is usually pretty straight forward
9:35 -- Debian and Ubuntu LTS are great server operating systems due to stability
11:07 -- Patching the project to use apt instead of pip for installing virtualenv
12:33 -- Forgetting to update the docs and using git commands to fix that
13:36 -- Using git add -p to have fine grain control of your git commits
15:26 -- Adding new tests to prevent future bugs that are similar
16:48 -- Using the -c flag with Python to directly run commands in the interpreter
18:20 -- Updating your changelog for the fixes and new additions
19:52 -- Testing your changes locally before pushing them to GitHub
23:11 -- Manually checking your new test function just to be safe
25:27 -- Pushing the changes to GitHub, but not creating a release yet
26:49 -- Creating a good git commit using your code editor for syntax highlighting
29:45 -- Really pushing it to GitHub after going through a mental checklist
30:40 -- Having CI hooked up to your repo is very useful, especially for pull requests
32:28 -- Encountering an unexpected error in CI due to a sketchy local testing env
33:39 -- Fixing the Python.h related error by installing python-dev
35:00 -- Backtracking and changing your mind from a previous commit
37:31 -- Moving forward and fixing the error that happened in our CI test
39:28 -- Re-running your local tests just as a sanity check
40:23 -- Fixing file permissions related to WSL making everything 755
42:48 -- Mentally re-tracing your commits before pushing
45:28 -- Scoping git add -p to a specific file
47:21 -- Pushing our 3 local commits to GitHub and checking Travis-CI again
48:17 -- Configuring Travis-CI to run your tests on a regular interval
50:58 -- Creating a proper release with the changelog and git tags
53:54 -- Updating the Ansible role on the Ansible Galaxy
56:17 -- Closing the issue and informing the issue submitter it's been fixed
56:58 -- Dealing with the Earth shattering reality that you pushed a broken release
58:23 -- Dropping support for Ubuntu 16.04 LTS since it's been EOL for a long time
1:01:19 -- Deciding not to push a 2nd new release since it affects so few cases

Reference links:

- [ Ссылка ]
- [ Ссылка ]
- [ Ссылка ]
- [ Ссылка ]
- [ Ссылка ]
- [ Ссылка ]

---

Follow along?

Personal Website: [ Ссылка ]
Twitter: [ Ссылка ]

свернуть