Skip to content

Revert "ci: disable Jekyll processing for GitHub Pages deployment" - #1366

Merged
NathanLovato merged 1 commit into
GDQuest:mainfrom
DevTwilight:revert-1365-fix-web-deployment
Aug 7, 2026
Merged

Revert "ci: disable Jekyll processing for GitHub Pages deployment"#1366
NathanLovato merged 1 commit into
GDQuest:mainfrom
DevTwilight:revert-1365-fix-web-deployment

Conversation

@DevTwilight

Copy link
Copy Markdown
Contributor

Reverts #1365

@DevTwilight

Copy link
Copy Markdown
Contributor Author

The .nojekyll file should be at the root of the gh-pages branch. I’ll create a new PR to fix this. Sorry about the mistake.

@DevTwilight

Copy link
Copy Markdown
Contributor Author

we no longer need the ci step so please update

@NathanLovato NathanLovato reopened this Aug 7, 2026
@NathanLovato
NathanLovato merged commit bcb75b0 into GDQuest:main Aug 7, 2026
2 checks passed
@NathanLovato

Copy link
Copy Markdown
Contributor

Okay I see thanks, my bad, I didn't understand why there were two separate PRs. Next time could you please keep things in a single PR/commit? Generally the generated LLM posts and multiple little PRs or commits add busywork we could avoid. I appreciate the help on these elements nonetheless, I'd just like to cut down the amount of parsing and bookkeeping I need to do on my end. One commit for one broad feature (let's say up to ~100-200 lines of changes as a guideline) is good.

@DevTwilight

DevTwilight commented Aug 7, 2026

Copy link
Copy Markdown
Contributor Author

i get it no worries

@NathanLovato

Copy link
Copy Markdown
Contributor

Thanks for your understanding!

@DevTwilight
DevTwilight deleted the revert-1365-fix-web-deployment branch August 7, 2026 12:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants