-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/add theme stackoverflow #32
Conversation
add support to manage birth data
Bug/manage birth data
Fixes typo for interests' summary
Since word breaks are not shown with a hyphen, this behaviour leads to a sloppy-looking CV.
Prevent word breaks in very long lines
Feature/improve docs and release
…mponents--mock-jwks chore(main): release 1.0.0
actually this is more a chore, but I need to produce a new release so fix
fix: release script
Release-As: 2.0.5
…mponents--mock-jwks chore(main): release 2.0.5
Update README.md
fix(docs): link to example deployment
feat: support keywords for work experience entries
…mponents--mock-jwks chore(main): release 2.1.0
…add-theme-stackoverflow
Important Auto Review SkippedDraft detected. Please check the settings in the CodeRabbit UI or the To trigger a single review, invoke the TipsChat with CodeRabbit Bot (
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
I am kinda trying something out here. I locally rewrote the history of my fork of the stackoverflow theme with: git filter-repo --to-subdirectory-filter themes/stackoverflow --tag-rename '':'@jsonresume/theme-stackoverflow' then I added the local folder as a remote for
and merged it by allowing an unrelated history.
So this way we can nicely "import" third party repositories into the codebase of the monorepo while even keeping the history (and the attribution to maintainers / creators etc.). I personally would embrace if my code was stored here as long as someone allows me to update it etc. and publishes it safely and securely. The question is: Will people approve of this approach? For example @phoinixi. What do you think @phoinixi? Would you be offended if we merged this and then published the code as And what about resumed? If we decided to make |
If the original authors would be up it with, there would be credit given in multiple places and collaborator access should be generally fine. It would help us get to a more symbiotic ecosystem more quickly when it comes to things like themes/stackoverflow/src/dateHelpers.tsx and i18n utils. When bumping schema changes, we could more easily update all of the "official" themes in a foul swoop also. |
No description provided.