fix: rework branch naming updating to next 16
Squashed commit of the following: commit13fb596232Author: SrJuggernaut <jugger@srjuggernaut.dev> Date: Thu Apr 2 12:59:26 2026 -0600 chore(deps): upgrade sharp to v0.34.5, add @types/bun, remove @types/node commit17be2f09ddAuthor: SrJuggernaut <jugger@srjuggernaut.dev> Date: Thu Apr 2 12:49:47 2026 -0600 chore: add lint-staged with husky pre-commit hook for automated linting commitb4a28fb35eAuthor: SrJuggernaut <jugger@srjuggernaut.dev> Date: Thu Apr 2 12:49:29 2026 -0600 chore: update husky hooks for latest version and use bun commit796c952890Author: SrJuggernaut <jugger@srjuggernaut.dev> Date: Thu Apr 2 12:00:41 2026 -0600 build: add Dockerfile and .dockerignore for Next.js containerization commit166ac4350fAuthor: SrJuggernaut <jugger@srjuggernaut.dev> Date: Thu Apr 2 11:59:44 2026 -0600 chore: moves next config to typescript Also adds DOCKER_BUILD env variable in prepare for moving out from github workflows commitea498588e0Author: SrJuggernaut <jugger@srjuggernaut.dev> Date: Wed Apr 1 14:17:22 2026 -0600 chore(deps): bump date-fns from 3.3.1 to 4.1.0 commit3c66b5bad1Author: SrJuggernaut <jugger@srjuggernaut.dev> Date: Wed Apr 1 14:16:31 2026 -0600 chore: update @pandacss/dev to v1.9.1 commit221034133dAuthor: SrJuggernaut <jugger@srjuggernaut.dev> Date: Wed Apr 1 14:14:35 2026 -0600 chore: update husky and commitlint commit4be0de62fcAuthor: SrJuggernaut <jugger@srjuggernaut.dev> Date: Wed Apr 1 14:07:57 2026 -0600 chore: update FontAwesome dependencies to v7.2.0 commitb595cba4b0Author: SrJuggernaut <jugger@srjuggernaut.dev> Date: Wed Apr 1 14:01:16 2026 -0600 chore: update TypeScript module config to esnext and bundler commitb8454f750dAuthor: SrJuggernaut <jugger@srjuggernaut.dev> Date: Wed Apr 1 13:51:25 2026 -0600 feat: add suspense loading state to recover password page commitd0f4a88661Author: SrJuggernaut <jugger@srjuggernaut.dev> Date: Wed Apr 1 13:48:15 2026 -0600 refactor: enhance TypeScript typing and import consistency commit57a6032a24Author: SrJuggernaut <jugger@srjuggernaut.dev> Date: Wed Apr 1 13:46:02 2026 -0600 chore: upgrade next and deps commitf8018048bcAuthor: SrJuggernaut <jugger@srjuggernaut.dev> Date: Wed Jul 31 18:44:51 2024 -0600 fix: pm2 run with bun commitec196b2850Author: SrJuggernaut <jugger@srjuggernaut.dev> Date: Wed Jul 31 18:35:29 2024 -0600 fix: deploy commit8802b0fd68Author: SrJuggernaut <jugger@srjuggernaut.dev> Date: Tue Jul 30 18:23:15 2024 -0600 feat: nextjs 14 (#20) * feat: eslint update * feat: start over and layout * feat: nextjs13 boilerplate * feat: static homepage * feat: static pages * feat: static unirse * chore: remove old mui types * chore: moving from yarn to bun * chore: update dependencies * feat: static equipo unirse * feat: move appwrite to entgamers-database package * feat: improve ui components * feat: update dependencies * feat: static login & register pages * fix: remove unused logs * feat: state redux toolkit & feedback slice * fix: equipo div inside p * feat: session * feat: metadataBase * feat: basic apply form * feat: http verbs * feat: recover password flow * chore: updated dependencies * fix: fix image config * fix: api team-applications route * fix: remove not longer used fonts * feat: session with current user * fix: login form recuperar contraseña * feat: equipo pages now uses data from database package * feat: useManageErrors hook * feat: updated cuenta page * chore: updated old formik forms to use hooks * feat: updated dependencies &package name * fix: session related bugs * fix: missing helper texts * feat: static applications dashboard * chore: update dependencies * refactor: team applications * fix: session api update commit14b52a7800Author: SrJuggernaut <jugger@srjuggernaut.dev> Date: Thu Sep 14 21:15:53 2023 -0600 fix: remove bundle analyzer commitf11ae1c4f3Author: SrJuggernaut <jugger@srjuggernaut.dev> Date: Thu Sep 14 21:08:33 2023 -0600 revert: revert to yarn to deploy commitf5a9a88f84Author: SrJuggernaut <jugger@srjuggernaut.dev> Date: Thu Sep 14 14:52:25 2023 -0600 fix: pm2 script commitf59a7cc091Author: SrJuggernaut <jugger@srjuggernaut.dev> Date: Thu Sep 14 14:49:04 2023 -0600 fix: interpreter to use pm2 2 commit3a831acaeeAuthor: SrJuggernaut <jugger@srjuggernaut.dev> Date: Thu Sep 14 14:39:51 2023 -0600 fix: interpreter to use pm2 commitb514c6bc6fAuthor: SrJuggernaut <jugger@srjuggernaut.dev> Date: Thu Sep 14 14:21:14 2023 -0600 fix: bun doesnt run on pm2 commitce87aa5ee3Author: SrJuggernaut <jugger@srjuggernaut.dev> Date: Thu Sep 14 14:14:12 2023 -0600 feat: moving deployments to bun commitb26d5d8ebaAuthor: SrJuggernaut <jugger@srjuggernaut.dev> Date: Thu Sep 14 13:01:22 2023 -0600 chore: updated dependencies commit390f8bc858Author: SrJuggernaut <jugger@srjuggernaut.dev> Date: Tue Jul 11 15:46:34 2023 -0600 feat: riot review commitd926d3a5efAuthor: SrJuggernaut <jugger@srjuggernaut.dev> Date: Wed Jan 4 15:47:45 2023 -0600 fix: github action name, wrong triggers commitfdefa84ec7Author: SrJuggernaut <jugger@srjuggernaut.dev> Date: Wed Jan 4 15:46:14 2023 -0600 fix: github action naming commit9db5e5cebfAuthor: SrJuggernaut <jugger@srjuggernaut.dev> Date: Wed Jan 4 15:44:18 2023 -0600 feat: setup github action to run on new server commit35105441cbAuthor: Jugger <jugger@srjuggernaut.dev> Date: Sun Oct 9 13:56:41 2022 -0500 docs: deploy env vars commit7986456b9cAuthor: Jugger <jugger@srjuggernaut.dev> Date: Sun Oct 9 13:20:42 2022 -0500 fix: production git ref commitf9aea7eea4Author: Jugger <jugger@srjuggernaut.dev> Date: Sat Oct 1 13:34:31 2022 -0500 fix: glass text contrast commita68098e7e2Author: Jugger <jugger@srjuggernaut.dev> Date: Sat Oct 1 13:33:29 2022 -0500 ci: use yarn instead npm commit864ff91255Author: Jugger <jugger@srjuggernaut.dev> Date: Fri Sep 30 19:32:40 2022 -0500 fix: server use isomorphic-fetch commitc69a166c1fAuthor: Jugger <jugger@srjuggernaut.dev> Date: Fri Sep 30 18:23:38 2022 -0500 revert: deploy as sudo Refs:624b225commit731c9b8962Author: Jugger <jugger@srjuggernaut.dev> Date: Fri Sep 30 17:50:41 2022 -0500 fix: pass only required env to deploy commit624b2251c4Author: Jugger <jugger@srjuggernaut.dev> Date: Fri Sep 30 13:57:27 2022 -0500 feat: post deploy as sudo commitb73cc51e08Author: Jugger <jugger@srjuggernaut.dev> Date: Fri Sep 30 13:41:56 2022 -0500 fix: pass environment to actions commita35e99f8ffAuthor: Jugger <jugger@srjuggernaut.dev> Date: Thu Sep 29 21:54:58 2022 -0500 ci: deploy using pm2 * ci: pm2 configuration file * ci: github action deploy preview * ci: github action deploy production * ci: env variables now pass to pm2 commit4f8c4f6492Author: Jugger <jugger@srjuggernaut.dev> Date: Wed Sep 28 18:09:10 2022 -0500 docs: initial documentation commitc3dae929c6Author: Jugger <jugger@srjuggernaut.dev> Date: Mon Sep 26 12:01:26 2022 -0500 feat: static site * feat: mui support & basic theming * feat: entgamers favicon * feat: public images until dynamic content can be used * feat: entgamers & gaming assets * feat: eslint extra rules * feat: mui theme modifications * feat: fontawesome, gsap, bundle analyzer * feat: common interfaces * feat: basic layout * chore: upadted dependencies * chore: updated dependencies * feat: updated link styles * feat: layout now have better interfaces * feat: basic seo component * feat: static website * feat: env variable rules in .gitignore * feat: added lint to pre-commit commit8573d61066Author: SrJuggernaut <jugger@srjuggernaut.dev> Date: Sat Aug 13 11:29:32 2022 -0500 Initial commit from Create Next App
This commit is contained in:
@@ -0,0 +1,87 @@
|
||||
|
||||
# Contributor Covenant Code of Conduct
|
||||
|
||||
## Our Pledge
|
||||
|
||||
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
|
||||
|
||||
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
|
||||
|
||||
## Our Standards
|
||||
|
||||
Examples of behavior that contributes to a positive environment for our community include:
|
||||
|
||||
* Demonstrating empathy and kindness toward other people
|
||||
* Being respectful of differing opinions, viewpoints, and experiences
|
||||
* Giving and gracefully accepting constructive feedback
|
||||
* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
|
||||
* Focusing on what is best not just for us as individuals, but for the overall community
|
||||
|
||||
Examples of unacceptable behavior include:
|
||||
|
||||
* The use of sexualized language or imagery, and sexual attention or advances of any kind in spaces not designated as NSFW
|
||||
* Trolling, insulting or derogatory comments, and personal or political attacks
|
||||
* Public or private harassment
|
||||
* Publishing others' private information, such as a physical or email address, without their explicit permission
|
||||
* Other conduct which could reasonably be considered inappropriate in a professional setting
|
||||
|
||||
## Enforcement Responsibilities
|
||||
|
||||
Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
|
||||
|
||||
Community leaders 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, and will communicate reasons for moderation decisions when appropriate.
|
||||
|
||||
## Scope
|
||||
|
||||
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces.
|
||||
Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
|
||||
|
||||
## Enforcement
|
||||
|
||||
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [contacto@entgamers.pro](mailto:contacto@entgamers.pro). All complaints will be reviewed and investigated promptly and fairly. All community leaders are obligated to respect the privacy and security of the reporter of any incident.
|
||||
|
||||
## Enforcement Guidelines
|
||||
|
||||
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
|
||||
|
||||
### 1. Correction
|
||||
|
||||
**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
|
||||
|
||||
**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
|
||||
|
||||
### 2. Warning
|
||||
|
||||
**Community Impact**: A violation through a single incident or series of
|
||||
actions.
|
||||
|
||||
**Consequence**: A warning with consequences for continued behavior. No
|
||||
interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
|
||||
|
||||
### 3. Temporary Ban
|
||||
|
||||
**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
|
||||
|
||||
**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
|
||||
|
||||
### 4. Permanent Ban
|
||||
|
||||
**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
|
||||
|
||||
**Consequence**: A permanent ban from any sort of public interaction within the community.
|
||||
|
||||
## Attribution
|
||||
|
||||
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
|
||||
|
||||
Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
|
||||
|
||||
For answers to common questions about this code of conduct, see the FAQ at
|
||||
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
|
||||
[https://www.contributor-covenant.org/translations][translations].
|
||||
|
||||
[homepage]: https://www.contributor-covenant.org
|
||||
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
|
||||
[Mozilla CoC]: https://github.com/mozilla/diversity
|
||||
[FAQ]: https://www.contributor-covenant.org/faq
|
||||
[translations]: https://www.contributor-covenant.org/translations
|
||||
Reference in New Issue
Block a user