zoukankan      html  css  js  c++  java
  • Understanding the GitHub Flow官方的是最好的,永远要看第一手资料

    On GitHub, saved changes are called commits.

    Understanding the GitHub Flow

    When you're working on a project, you're going to have a bunch of different features or ideas in progress at any given time – some of which are ready to go, and others which are not.

    Branching exists to help you manage this workflow.

    When you create a branch in your project, you're creating an environment where you can try out new ideas. 

    Changes you make on a branch don't affect the master branch, so you're free to experiment and commit changes, safe in the knowledge that your branch won't be merged until it's ready to be reviewed by someone you're collaborating with.

    ProTip

    Branching is a core concept in Git, and the entire GitHub Flow is based upon it. There's only one rule: anything in the master branch is always deployable.

    Because of this, it's extremely important that your new branch is created off of master when working on a feature or a fix. Your branch name should be descriptive (e.g., refactor-authenticationuser-content-cache-keymake-retina-avatars), so that others can see what is being worked on.

    Commits also create a transparent history of your work that others can follow to understand what you've done and why.

    ProTip

    Commit messages are important, especially since Git tracks your changes and then displays them as commits once they're pushed to the server. 

    Again:官方的是最好的,永远要看第一手资料

  • 相关阅读:
    dock 安装部署和初级管理命令
    3 gogs+jenkins 触发远程构建及tomcat管理war包替换
    2 gitlab+jenkins maven自动打包更新
    1 gitlab+jenkins 自动化部署 持续集成
    Day7 面向对象进阶
    Day 6 面向对象初级
    day4 迭代器&生成器&递归&json&正则
    day5 常用模块
    day3 函数
    day2 数据及文件操作
  • 原文地址:https://www.cnblogs.com/liuzc/p/6978792.html
Copyright © 2011-2022 走看看