You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I found\n\nCONTRIBUTING.md still contains the literal placeholder:\n\ntext\nFIXME contribution guidelines like in other LB projects\n\n\nThe file does contain useful project tips later on, but it does not document the repository-specific contribution workflow.\n\n## Why this matters\n\nNew contributors cannot tell which branch/PR conventions, formatting and test commands, review expectations, or CLA/licensing steps apply to this SDK. The existing build-token notes are also difficult to use without a canonical contribution path.\n\n## Suggested fix\n\nReplace the placeholder with either the actual workflow (including validation commands and where to ask questions) or a link to the canonical Lightbend contribution guide, and keep the repository-specific build/sample instructions below it.
What I found\n\n
CONTRIBUTING.mdstill contains the literal placeholder:\n\ntext\nFIXME contribution guidelines like in other LB projects\n\n\nThe file does contain useful project tips later on, but it does not document the repository-specific contribution workflow.\n\n## Why this matters\n\nNew contributors cannot tell which branch/PR conventions, formatting and test commands, review expectations, or CLA/licensing steps apply to this SDK. The existing build-token notes are also difficult to use without a canonical contribution path.\n\n## Suggested fix\n\nReplace the placeholder with either the actual workflow (including validation commands and where to ask questions) or a link to the canonical Lightbend contribution guide, and keep the repository-specific build/sample instructions below it.