repurpose lazygit code

jesseduffield · May 12, 2019 · cf5ec171979d13a22aee6fcf435e655a085ab934 · cf5ec17
1 parent 62f3a5d
commit cf5ec171979d13a22aee6fcf435e655a085ab934
Unified Split

Showing 1,206 changed files with 398,563 additions and 2 deletions.
diff --git a/CODE-OF-CONDUCT.md b/CODE-OF-CONDUCT.md
@@ -0,0 +1,74 @@
+  
+# Contributor Covenant Code of Conduct
+  
+
+  
+## Our Pledge
+  
+
+  
+In the interest of fostering an open and welcoming environment, we as
+  
+contributors and maintainers pledge to making participation in our project and
+  
+our community a harassment-free experience for everyone, regardless of age, body
+  
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+  
+level of experience, education, socio-economic status, nationality, personal
+  
+appearance, race, religion, or sexual identity and orientation.
+  
+
+  
+## Our Standards
+  
+
+  
+Examples of behavior that contributes to creating a positive environment
+  
+include:
+  
+
+  
+* Using welcoming and inclusive language
+  
+* Being respectful of differing viewpoints and experiences
+  
+* Gracefully accepting constructive criticism
+  
+* Focusing on what is best for the community
+  
+* Showing empathy towards other community members
+  
+
+  
+Examples of unacceptable behavior by participants include:
+  
+
+  
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  
+  advances
+  
+* Trolling, insulting/derogatory comments, and personal or political attacks
+  
+* Public or private harassment
+  
+* Publishing others' private information, such as a physical or electronic
+  
+  address, without explicit permission
+  
+* Other conduct which could reasonably be considered inappropriate in a
+  
+  professional setting
+  
+
+  
+## Our Responsibilities
+  
+
+  
+Project maintainers are responsible for clarifying the standards of acceptable
+  
+behavior and are expected to take appropriate and fair corrective action in
+  
+response to any instances of unacceptable behavior.
+  
+
+  
+Project maintainers have the right and responsibility to remove, edit, or
+  
+reject comments, commits, code, wiki edits, issues, and other contributions
+  
+that are not aligned to this Code of Conduct, or to ban temporarily or
+  
+permanently any contributor for other behaviors that they deem inappropriate,
+  
+threatening, offensive, or harmful.
+  
+
+  
+## Scope
+  
+
+  
+This Code of Conduct applies both within project spaces and in public spaces
+  
+when an individual is representing the project or its community. Examples of
+  
+representing a project or community include using an official project e-mail
+  
+address, posting via an official social media account, or acting as an appointed
+  
+representative at an online or offline event. Representation of a project may be
+  
+further defined and clarified by project maintainers.
+  
+
+  
+## Enforcement
+  
+
+  
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+  
+reported by contacting the [project leader](https://github.com/jesseduffield). 
+  
+All complaints will be reviewed and investigated and will result in a response that
+  
+complaints will be reviewed and investigated and will result in a response that
+  
+is deemed necessary and appropriate to the circumstances. The project team is
+  
+obligated to maintain confidentiality with regard to the reporter of an incident.
+  
+Further details of specific enforcement policies may be posted separately.
+  
+
+  
+Project maintainers who do not follow or enforce the Code of Conduct in good
+  
+faith may face temporary or permanent repercussions as determined by other
+  
+members of the project's leadership.
+  
+
+  
+## Attribution
+  
+
+  
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+  
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+  
+
+  
+[homepage]: https://www.contributor-covenant.org
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -0,0 +1,37 @@
+  
+# Contributing
+  
+
+  
+♥ We love pull requests from everyone !
+  
+
+  
+When contributing to this repository, please first discuss the change you wish
+  
+to make via issue, email, or any other method with the owners of this repository
+  
+before making a change.
+  
+
+  
+## So all code changes happen through Pull Requests
+  
+
+  
+Pull requests are the best way to propose changes to the codebase. We actively
+  
+welcome your pull requests:
+  
+
+  
+1. Fork the repo and create your branch from `master`.
+  
+2. If you've added code that should be tested, add tests.
+  
+3. If you've added code that need documentation, update the documentation.
+  
+4. Make sure your code follows the [effective go](https://golang.org/doc/effective_go.html) guidelines as much as possible.
+  
+5. Be sure to test your modifications.
+  
+6. Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+  
+7. Issue that pull request!
+  
+
+  
+## Code of conduct
+  
+
+  
+Please note by participating in this project, you agree to abide by the [code of conduct].
+  
+
+  
+[code of conduct]: https://github.com/jesseduffield/lazydocker/blob/master/CODE-OF-CONDUCT.md
+  
+
+  
+## Any contributions you make will be under the MIT Software License
+  
+
+  
+In short, when you submit code changes, your submissions are understood to be
+  
+under the same [MIT License](http://choosealicense.com/licenses/mit/) that
+  
+covers the project. Feel free to contact the maintainers if that's a concern.
+  
+
+  
+## Report bugs using Github's [issues](https://github.com/jesseduffield/lazydocker/issues)
+  
+
+  
+We use GitHub issues to track public bugs. Report a bug by [opening a new
+  
+issue](https://github.com/jesseduffield/lazydocker/issues/new); it's that easy!
diff --git a/Dockerfile b/Dockerfile
@@ -0,0 +1,15 @@
+  
+# run with:
+  
+# docker build -t lazydocker .
+  
+# docker run -it lazydocker:latest /bin/sh -l
+  
+
+  
+FROM golang:alpine
+  
+WORKDIR /go/src/github.com/jesseduffield/lazydocker/
+  
+COPY ./ .
+  
+RUN CGO_ENABLED=0 GOOS=linux go build
+  
+
+  
+FROM alpine:latest
+  
+RUN apk add -U git xdg-utils
+  
+WORKDIR /go/src/github.com/jesseduffield/lazydocker/
+  
+COPY --from=0 /go/src/github.com/jesseduffield/lazydocker /go/src/github.com/jesseduffield/lazydocker
+  
+COPY --from=0 /go/src/github.com/jesseduffield/lazydocker/lazydocker /bin/
+  
+RUN echo "alias gg=lazydocker" >> ~/.profile