gitea.git - Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD: https://github.com/go-gitea/gitea

summary refs log tree commit diff stats

path: root/models/gpg_key.go

	Commit message (Expand)	Author	Age	Files	Lines
*	Show Signer in commit lists and add basic trust (#10425)	zeripath	2020-02-27	1	-3/+40
*	API add/generalize pagination (#9452)	SpaWn2KiLl	2020-01-24	1	-4/+9
*	Ensure default gpg settings not nil and found commits have reference to repo ...	zeripath	2019-10-20	1	-0/+2
*	Upgrade xorm to v0.8.0 (#8536)	Lunny Xiao	2019-10-17	1	-1/+1
*	Sign merges, CRUD, Wiki and Repository initialisation with gpg key (#7631)	zeripath	2019-10-16	1	-67/+292
*	Display ui time with customize time location (#7792)	Lunny Xiao	2019-08-15	1	-14/+14
*	Fix wrong GPG expire date (#6643)	Antoine GIRARD	2019-04-15	1	-6/+11
*	add .gpg url (match github behaviour) (#6610)	Antoine GIRARD	2019-04-14	1	-18/+79
*	Better logging (#6038) (#6095)	zeripath	2019-04-02	1	-6/+6
*	move code.gitea.io/git to code.gitea.io/gitea/modules/git (#6364)	Lunny Xiao	2019-03-27	1	-1/+1
*	Fix null pointer dereference in ParseCommitWithSignature (#4962)	SagePtr	2018-09-20	1	-1/+1
*	Don't write to log NoCommitterAccount (#3621)	Morgan Bazalgette	2018-03-04	1	-1/+5
*	Refactor struct's time to remove unnecessary memory usage (#3142)	Lunny Xiao	2017-12-11	1	-22/+14
*	GPG key email verification no longer case sensitive (#2661) (#2663)	Julian Scholle	2017-10-06	1	-1/+2
*	Replace deprecated Id method with ID (#2655)	Ethan Koenig	2017-10-05	1	-1/+1
*	Use AfterLoad instead of AfterSet on Structs (#2628)	Lunny Xiao	2017-10-01	1	-11/+9
*	Fix lint errors (#2547)	Ethan Koenig	2017-09-19	1	-5/+1
*	Only check at least one email gpg key (#2266)	Antoine GIRARD	2017-09-05	1	-9/+27
*	remove unnecessary blank lines and wrong error log	Lunny Xiao	2017-06-28	1	-3/+1
*	Refactor session close as xorm already does everything needed internally (#2020)	Lauris BH	2017-06-21	1	-2/+2
*	Fix GPG email checking to be case insensitive (#1988)	Lauris BH	2017-06-17	1	-2/+2
*	Switch to keybase go-crypto (for some elliptic curve key) + test (#1925)	Antoine GIRARD	2017-06-14	1	-3/+3
*	Rework SSH key management UI to add GPG (#1293)	Antoine GIRARD	2017-04-26	1	-12/+21
*	GPG commit validation (#1150)	Antoine GIRARD	2017-03-22	1	-0/+186
*	fix gpg wrong column types	Lunny Xiao	2017-03-20	1	-2/+2
*	Implement GPG api (#710)	Antoine GIRARD	2017-03-16	1	-0/+276

.** - Interpret the arguments of others in good faith, do not seek to disagree. - When we do disagree, try to understand why. - **Be constructive.** - Avoid derailing: stay on topic; if you want to talk about something else, start a new conversation. - Avoid unconstructive criticism: don't merely decry the current state of affairs; offer—or at least solicit—suggestions as to how things may be improved. - Avoid snarking (pithy, unproductive, sniping comments) - Avoid discussing potentially offensive or sensitive issues; this all too often leads to unnecessary conflict. - Avoid microaggressions (brief and commonplace verbal, behavioral and environmental indignities that communicate hostile, derogatory or negative slights and insults to a person or group). - **Be responsible.** - What you say and do matters. Take responsibility for your words and actions, including their consequences, whether intended or otherwise. People are complicated. You should expect to be misunderstood and to misunderstand others; when this inevitably occurs, resist the urge to be defensive or assign blame. Try not to take offense where no offense was intended. Give people the benefit of the doubt. Even if the intent was to provoke, do not rise to it. It is the responsibility of all parties to de-escalate conflict when it arises. ## 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, 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, as well as to ban (temporarily or permanently) any contributor for 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. This Code of Conduct also applies outside the project spaces when the Project Stewards have a reasonable belief that an individual’s behavior may have a negative impact on the project or its community. ### Conflict Resolution We do not believe that all conflict is bad; healthy debate and disagreement often yield positive results. However, it is never okay to be disrespectful or to engage in behavior that violates the project’s code of conduct. If you see someone violating the code of conduct, you are encouraged to address the behavior directly with those involved. Many issues can be resolved quickly and easily, and this gives people more control over the outcome of their dispute. If you are unable to resolve the matter for any reason, or if the behavior is threatening or harassing, report it. We are dedicated to providing an environment where participants feel welcome and safe. Reports should be directed to the Gitea Project Stewards at conduct@gitea.com. It is the Project Stewards’ duty to receive and address reported violations of the code of conduct. They will then work with a committee consisting of representatives from the technical-oversight-committee. We will investigate every complaint, but you may not receive a direct response. We will use our discretion in determining when and how to follow up on reported incidents, which may range from not taking action to permanent expulsion from the project and project-sponsored spaces. Under normal circumstances, we will notify the accused of the report and provide them an opportunity to discuss it before any action is taken. If there is a consensus between maintainers that such an endeavor would be useless (i.e. in case of an obvious spammer), we reserve the right to take action without notifying the accused first. The identity of the reporter will be omitted from the details of the report supplied to the accused. In potentially harmful situations, such as ongoing harassment or threats to anyone’s safety, we may take action without notice. ### Attribution This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html ## Summary - Treat everyone with respect and kindness. - Be thoughtful in how you communicate. - Don’t be destructive or inflammatory. - If you encounter an issue, please mail conduct@gitea.com.