git --version #查看git软件版本 git version 2.39.1 ★全局设置 设置用户名和邮箱，只用于提交commit时做metadata信息，不用于身份验证 #全局设置信息保存在 ~/.gitconfig 文件里 # git config --global user.name cof # git status #查看当前工作目录和暂存区的状态 On branch master No commits yet nothing to commit (create/copy files and use "git add" to track) # echo 'print("hello world")' > main.py # git commit -m "msgxxx" #将暂存区提交到仓库区（commit为提交操作），- m后指定本次提交的说明信息 1 file changed, 1 inser�on(+) create mode 100644 main.py # git log #查看提交记录；显示完整的hash值 commit 7b8ff6

be more production-like in a consistent and repeatable wayiii. Building a deployment pipeline 1. Commit stage – build & package software, runs automated unit tests, and code quality (static analysis, development, 78% reduction in cost per program c. SMALL BATCH DEVELOPMENT AND WHAT HAPPENS WHEN WE COMMIT CODE TO TRUNK INFREQUENTLY i. Branching Strategies 1. Optimize for individual productivity – everyone difficult 2. Optimize for team productivity – everyone works in common area, simpler commits, but each commit can break the entire project ii. When merging is difficult, less able to refactor due to potential

“What’s a good compromise? It seems that the best course might be to give people an opportunity to commit up front to their preferred path of action. This approach might not be as effective as the dictatorial

Review Guidelines 1. Everyone must have someone review their changes2. Everyone should monitor the commit stream of their fellow team members to identify issues 3. Define changes which qualify as high-risk

rowcount", sqlite_cursor.rowcount) # 游标上 一次执行时返回的结果，刚插入一条数据，所以显示1 sqlite_cursor.close() sqlite_conn.commit() # 保存 sqlite_conn.close() # 关闭连接 sqlite_conn2 = sqlite3.connect('test.db') # 连接数据库（此 时数据库文件已存在）