Skip to content

corekube/web

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

88 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

#Pull Request Guidelines

  • All pull requests should be a single commit, so that the changes can be observed and evaluated together. Here's the best way to make that happen:

    • Pull from this repo's 'master' branch to your local repo. All pull requests must be against the 'master' branch.
    • Create a local branch for making your changes:
      • git checkout master
      • git checkout -b mychangebranch
    • Do all your testing, fixing, etc., in that branch. Make as many commits as you need as you work.
    • When you've completed your changes, and and made sure that everything's working great, merge it back into working using the '--squash' option so that it appears as a single commit.
      • git checkout master
      • git merge --squash mychangebranch
      • git commit -am "Added super powers"
      • git push origin master
    • Now you have your changes in a single commit against your 'master' branch on GitHub, and can create the pull request.
  • Posts submitted should be in Markdown with the following format:

    • File must be placed in: content/posts/
    • File must have a filename similar to: 2016_01_01-my-first-post.md
    • The post must include: its metadata, its summary, and a fold defined by the line <!--more-->, as such:
      +++
      date = "2016-01-01T00:00:00-08:00"
      tags = ["Development", "golang"]
      title = "My First Post"
      slug = "my-first-post"
      authors = "John Smith"
      +++
      
      This is my summary
      
      <!--more-->
      
      Hello World.
      

About

website content for https://corekube.com

License

Contributing

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 3

  •  
  •  
  •  

Languages