Closed prplwtf closed 1 month ago
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
docs | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Jun 19, 2024 4:52pm |
Name | Link |
---|---|
Latest commit | 35c9ff3d41e2a043b0656cdb575088a5207b85b9 |
Latest deploy log | https://app.netlify.com/sites/pelica/deploys/66730cae0a841a0008a55b1a |
Deploy Preview | https://deploy-preview-60--pelica.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
when merge
This has practically been reverted in commit ce341b8483cf129e3409eb521b07317c9da4f67b right after being merged.
Pelicans team doesn't seem very good ngl
I see no reason to go into the whole objectives and goals do not align when it's a FAQ.
It's a simple no, they will not work.
I'll drop this topic for now, but merging something and then completely editing something afterwards (which feels like a way to silence a pull request) isn't the nicest thing to do. Recommending changes in my wording and discussing/suggesting better alternatives would've been more appreciated.
This pull request has been made as the current Blueprint FAQ section incorrectly reflects the state of things:
I've corrected this to the following:
The current answer incorrectly assumes that I am responsible for making all extensions work with Pelican, which is incorrect. In my previous PR, I talked about how we didn't have the manpower to port Blueprint over (if Pelican were to align with our goals), not that we didn't have the time to migrate extensions over.
If there are any changes needed that are preventing this PR from getting merged, please let me know.