docs: include versioning details and migration guides in the readme#410
docs: include versioning details and migration guides in the readme#410
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #410 +/- ##
=======================================
Coverage 99.85% 99.85%
=======================================
Files 7 7
Lines 702 702
=======================================
Hits 701 701
Misses 1 1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
WilliamBergamin
left a comment
There was a problem hiding this comment.
Nice 🚀 great job!!
|
@WilliamBergamin Thanks a ton! But all credit to @thejeff77 for suggesting that this info be included in the I'll go ahead with a merge now, but I'm so open to revisiting how or even where this information is organized later 📚 ✨ |
|
Thanks folks! I have some additional tidbits to share, unfortunately with a lot of the inputs moving to the payload, actionlint is much less helpful in verifying if the action is still valid after migration. Requires a lot of trial and error. It would be pretty cool if chatGPT or Copilot could be trained up on migrations to make this a bit more automated. I'm sure it will get there at some point anyway. Hints on checking validity locally without having to commit, push, run would be welcome! (If they exist) |
Summary
This PR adds a migration guide to the
READMEand a "table of contents" to find fast links between section headers 👾 ✨Following #398!
Preview
🔗 https://github.com/slackapi/slack-github-action/tree/docs-migration-guide
Requirements