Home

IO-Link C4/PG52 - JSON Integration

Next Release Q1/2025 Q3/2025

• general fixes and improvements
• MQTT extensions
• Async API specification for MQTT
• Wireless additions

Workflow

More information

• in general git branching model is applied (see https://nvie.com/posts/a-successful-git-branching-model/)
• very editor can be used to apply changes, e.g. visual studio code (https://code.visualstudio.com/)
• VS Code has also a git extension (see https://code.visualstudio.com/docs/sourcecontrol/overview)
• Open API extension (https://marketplace.visualstudio.com/items?itemName=42Crunch.vscode-openapi)
• Linter extension (spectral) (https://marketplace.visualstudio.com/items?itemName=stoplight.spectral)

Git Naming Convention / Branch Naming

• Must:

  • Include a short descriptive summary in imperative present tense
  • Use Hyphens for separating words

• May:

  • Include the work type: feature, refactor, bugfix, hotfix, etc.
  • Include corresponding ticket/story id (e.g. from Jira, GitHub issue, etc.)
  • Suggested Forma: {work type e.g.}/{2-3 word summary}/{story or ticket id}_

Example: git checkout -b feature/oauth-migration/ATL-244

Review process

• https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request