I recently started to contribute on open-source projects on GitHub.
Here is the summary of the recent things I made
Note: click on arrow to unfold each category
Some PR about forgit improvements
Add FORGIT_STASH_SHOW_PREVIEW_GIT_OPTS
#389
Check list
- [X] I have performed a self-review of my code
- [ ] I have commented my code in hard-to-understand areas
- [X] I have made corresponding changes to the documentation
Description
FORGIT_STASH_SHOW_PREVIEW_GIT_OPTS variable can be used to tune the rendering of a stash preview.
The following example allows listing the content of the stash before opening it.
FORGIT_STASH_SHOW_PREVIEW_GIT_OPTS="--patch-with-stat --stat-count=10"
Type of change
- [ ] Bug fix
- [X] New feature
- [ ] Refactor
- [ ] Breaking change
- [ ] Documentation change
Test environment
- Shell
- [ ] bash
- [ ] zsh
- [X] fish
- OS
- [X] Linux
- [ ] Mac OS X
- [ ] Windows
- [ ] Others:
Feature request: add preview settings everywhere
#391
Check list
- [X] I have read through the README
- [X] I have the latest version of forgit
- [X] I have searched through the existing issues
Idea
I worked on implementing #389, would like me to add something equivalent to forgit log
and other commands ?
Improved sphinxdoc tooltip plugin extension
✨ Add support for duration and delay tippy_props
#18
Fixes #17
also fix documentation about arrow and code about theme
View on GitHubMany code reviews
Upgrade code to respect new conventions.
#111
go.mod refers to 1.17, so we can use os.ReadFile and os.WriteFile instead of ioutil.ReadFile and ioutil.WriteFile that are now deprecated.
We should use errors.As since go 1.13 otherwise any wrapped errors won't be caught.
View on GitHub
Use JSONL format for New Line Delimited JSON
#112
https://en.wikipedia.org/wiki/JSON_streaming
View on GitHub
receiver cleanup
#522
- Refactor to use consistent parserState receiver
- Clean unused receivers
Fix test helpers
#523
Test helpers should use t.Helper()
This way if an error occurs it would be reported outside the helper
View on GitHubMany PR about typos fixing or installing GitHub actions to validate spellchecking on various repositories
fix typos
#4
- Fix typos and style
- Format README.md file
Add Typos GitHub Action
#37
https://github.com/marketplace/actions/typos-action
Fixes #28
View on GitHub
fix typos
#113
- Fix typos in code and tests
- Fix acronyms and brand names
fix typos, brands and acronyms
#21
- fix typos in code, test and documentation
- Fix registered trademark and other acronyms
Fix typos in the documentation and code comments
#99
typos suggestion
#390
Check list
- [X] I have performed a self-review of my code
- [ ] I have commented my code in hard-to-understand areas
- [X] I have made corresponding changes to the documentation
Description
- Fix some typos and wordings in README.md
- Fix headers style
- Fix exemplī grātiā usage (Latin)
Type of change
- [ ] Bug fix
- [ ] New feature
- [ ] Refactor
- [ ] Breaking change
- [X] Documentation change
Test environment
- Shell
- [ ] bash
- [ ] zsh
- [ ] fish
- OS
- [ ] Linux
- [ ] Mac OS X
- [ ] Windows
- [ ] Others:
Fix typo and style
#3
Follow me on dev.to, follow me on GitHub: ccoVeille
Top comments (1)
Nice idea! Thanks for sharing.