βΊΛ βΈβΈ About Me βΈβΈ βΊΛ
- I go by Nathan
- I live in California
- My favorite games is League of Legends & Majora's Mask
βΊΛ βΈβΈ Career Goals βΈβΈ βΊΛ
- Joining a team at a established company
- Building my skills as a programmer and becoming a professional developer
βΊΛ βΈβΈ Collaborate βΈβΈ βΊΛ
- I'm looking to collaborate on full-stack projects
- Mainly JS/TS, however open to all stacks!
π»ππππππππππ π·ππππππππ
κ°Κα΄Ι΄α΄-α΄Ι΄α΄ α΄ α΄α΄ α΄Κα΄α΄α΄α΄Ι΄α΄
πΉπππ-πΌππ π»ππ§πππ π‘ππππ₯
οΌ€ο½ ο½ο½ο½ο½ο½ο½ ο½ο½
πΈππππππ½πΎππ πΈπππ
ππΌπΊπΊπΆπ ππΌπ»ππ²π»ππΆπΌπ»π
I try to use a style of semmantic commit messages for all of my commits in my repo
Format:category(optional scope or module): message
feat / feature:all changes that introduce completely new code or new featuresfix:changes that fix a bug (ideally will additionally reference an issue if present)refactor:any code related change that is not a fix or a featuredocs:changing existing or creating new documentation (i.e. README, docs for usage of a lib or cli usage)build:all changes regarding the build of the software, changes to dependencies or the addition of new dependenciestest:all changes regarding tests (adding new tests or changing existing ones)ci:all changes regarding the configuration of continuous integration (i.e. github actions, ci system)z:all changes to the repository that do not fit into any of the above categories
feat(components): add new prop to the avatar component