Cloudflare next - Githubissues

rotimi-best commented 2 weeks ago

What does this PR do?

Deploy docs to cloudflare.

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Chore (refactoring code, technical debt, workflow improvements)
[ ] Enhancement (small improvements)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change adds a new database migration
[ ] This change requires a documentation update

How should this be tested?

Test A
Test B

Checklist

Required

[ ] Filled out the "How to test" section in this PR
[ ] Self-reviewed my own code
[ ] Commented on my code in hard-to-understand bits
[ ] Ran pnpm build
[ ] Checked for warnings, there are none
[ ] Removed all console.logs
[ ] Merged the latest changes from main onto my branch with git pull origin main
[ ] My changes don't cause any responsiveness issues

Appreciated

[ ] If a UI change was made: Added a screen recording or screenshots to this PR
[ ] Updated the ClassroomIO Docs if changes were necessary

vercel[bot] commented 2 weeks ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
cio-cloud	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 18, 2024 3:22am
cio-com	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 18, 2024 3:22am
cio-docs	❌ Failed (Inspect)			Jun 18, 2024 3:22am

github-actions[bot] commented 2 weeks ago

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "Cloudflare next". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

rotimi-best commented 2 weeks ago

Closing because Cloudflare was having very weird behaviour with deploying docs and classroomio-com.

In addition I have moved back to vercel so we can support *.classroomio.com

rotimi-best / classroomio