Brak opisu

Yoginth 5c6b6390c0 1.0.2-prod-rc.16 7 lat temu
.gitote 76283dce48 Updated Issue Template 7 lat temu
.vscode e7c1d4579d Fixing Go Report Card Issues #100 7 lat temu
cmd e76dc63d69 Updated License in all code head comments 7 lat temu
conf 8ab8ee6827 Updated from 2018 -> 2019 in Licenses 7 lat temu
docker d5db430075 Removed Readme in Finalize 7 lat temu
docs ba47fdf98e Moved Stack to Docs 7 lat temu
models e76dc63d69 Updated License in all code head comments 7 lat temu
pkg e76dc63d69 Updated License in all code head comments 7 lat temu
public 49d108f2dc Removed Drift 7 lat temu
routes e76dc63d69 Updated License in all code head comments 7 lat temu
script 7077d0613d Added UsercontentURL 7 lat temu
templates 49d108f2dc Removed Drift 7 lat temu
vendor 7f6a493591 Merge branch 'master' of https://gitote.in/gitote/gitote 7 lat temu
.dockerignore 2dcc9bb315 Updated Docker Ignore file 7 lat temu
.gitattributes bc701732b4 Initial Commit 7 lat temu
.gitignore 1ec1e45233 Removed Logs 7 lat temu
.gitlab-ci.yml fe40e35bc9 Removed Unused CI Tests 7 lat temu
CONTRIBUTING.md 9959bc643f Updated Contributing file 7 lat temu
Dockerfile 1ce83c3c3a Removed deprecated MAINTAINER in dockerfile and Resolves #86 7 lat temu
LICENSE a0bc068da3 Updated License Year Format 7 lat temu
Makefile 542bbbbd8c Removed Night Mode 7 lat temu
Procfile 88f8515e5d Updated Procfile 7 lat temu
README.md dd022e1065 Update 'README.md' 7 lat temu
appveyor.yml ca280c7fe7 Updated Appveyor Path 7 lat temu
gitote.go 5c6b6390c0 1.0.2-prod-rc.16 7 lat temu

README.md

Git + Rem(ote) = Gitote ❤️

Software version control made simple!

Welcome to the gitote codebase. We are so excited to have you. With your help, we can build out Gitote to be more stable and better serve our platform.

Shields 🛡

Linux Windows Go Report Codacy Donate
GitLab Build status AppVeyor Build status Go Report Codacy Badge Liberapay

Docker 🐬

Downloads Quay Azure
Downloads Quay Build status

Versions 📦

GoLang PostgreSQL Git
GoLang PostgreSQL Git

What is gitote ❓

Gitote is an open source end-to-end software development platform with built-in version control, issue tracking, code review, and more.

Table of Contents

Contributing 🚧

We expect contributors to abide by our underlying code of conduct. All conversations and discussions on Gitote (issues, pull requests) and across Gitote must be respectful and harassment-free.

Where to contribute

When in doubt, ask a core team member! You can mention us in any issues . Any issue with Good first Issue tag is typically a good place to start.

Refactoring code, e.g. improving the code without modifying the behavior is an area that can probably be done based on intuition and may not require much communication to be merged.

🐞 Fixing bugs may also not require a lot of communication, but the more the better. Please surround bug fixes with ample tests. Bugs are magnets for other bugs. Write tests near bugs!

🏗 Building features is the area which will require the most communication and/or negotiation. Every feature is subjective and open for debate. As always, when in doubt, ask!

How to contribute

  1. Fork the project & clone locally. Follow the initial setup here.
  2. Create a branch, naming it either a feature or bug: git checkout -b feature/that-new-feature or bug/fixing-that-bug
  3. Code and commit your changes. Bonus points if you write a good commit message: git commit -m 'Add some feature'
  4. Push to the branch: git push origin feature/that-new-feature
  5. Create a pull request for your branch 🎉

Contribution guideline 📜

Create an issue

Nobody's perfect. Something doesn't work? Or could be done better? Let us know by creating an issue.

PS: a clear and detailed issue gets lots of love, all you have to do is follow the issue template!

Clean code with tests

Some existing code may be poorly written or untested, so we must have more scrutiny going forward. We test with go test, let us know if you have any questions about this!

Create a pull request

  • Try to keep the pull requests small. A pull request should try its very best to address only a single concern.
  • Make sure all tests pass and add additional tests for the code you submit.
  • Document your reasoning behind the changes. Explain why you wrote the code in the way you did. The code should explain what it does.
  • If there's an existing issue related to the pull request, reference to it by adding something like References/Closes/Resolves #305, where 305 is the issue number.
  • If you follow the pull request template, you can't go wrong.

Codebase 💻

The stack

View Gitote tech stack here

Documentation 📑

View Gitote documentations here

Features 🔮

  • Activity timeline
  • SSH and HTTP/HTTPS protocols
  • Account/Organization/Repository management
  • Add/Remove repository collaborators
  • Repository/Organization webhooks (including Slack and Discord)
  • Repository Git hooks/deploy keys
  • Repository issues, pull requests, wiki and protected branches
  • Migrate and mirror repository and its wiki
  • Web editor for repository files and wiki
  • Jupyter Notebook
  • Two-factor authentication
  • Gravatar and Federated avatar with custom source
  • Mail service
  • More emojis. 🐈

Core team 👬

Sponsors 🤗

Thanks 🙏

License 💼

This program is free software: you can redistribute it and/or modify it under the terms of the MIT License. Please see the LICENSE file in our repository for the full text.

Happy Coding ❤️