Skip to main content
You’re not alone in this. The Baton community is active and welcoming.

Getting help

GitHub discussions

The primary place for questions and discussions is GitHub:
RepositoryUse for
baton-sdkSDK questions, general connector development
Specific connector reposIssues with that connector
Before asking:
  1. Search existing issues and discussions
  2. Check this documentation
  3. Review the recipes for common patterns

What makes a good question

Include:
  • What you’re trying to accomplish
  • What you’ve tried
  • Error messages (full text, not screenshots)
  • Relevant code snippets
  • Connector version and target system
Bad: “My connector doesn’t work” Good: “Sync fails with ‘unauthorized’ error when listing users. Using baton-okta v0.5.2 with API token auth. Token has read_users scope. Full error: [paste error]“

Support channels

ChannelResponse timeUse for
GitHub IssuesDaysBugs, feature requests
GitHub DiscussionsDaysQuestions, how-to help
ConductorOne SupportHoursProduction issues (customers)

Reporting issues

Bug reports

When reporting a bug, include:
InformationWhy it helps
Connector name and versionReproducibility
Steps to reproduceRoot cause analysis
Expected vs actual behaviorUnderstanding the issue
Error messagesDebugging
Environment (OS, Go version)Platform-specific issues
Template:
## Bug Report

**Connector:** baton-yourservice v1.2.3
**Environment:** macOS 14.0, Go 1.23

**Steps to reproduce:**
1. Configure connector with API key
2. Run `baton-yourservice --api-key $KEY`
3. Observe error

**Expected:** Sync completes successfully
**Actual:** Sync fails with error: [paste error]

**Logs:** (if helpful)

Feature requests

For new features:
  1. Check if the feature already exists (search issues)
  2. Describe the use case, not just the solution
  3. Explain why existing approaches don’t work
Good feature requests describe the problem:
  • “I need to sync custom attributes from Okta user profiles so that access reviews show department information”
Not just the solution:
  • “Add custom attribute support”

Security issues

DO NOT file security issues publicly.
Report security vulnerabilities to: security@conductorone.com Security researchers are publicly acknowledged for responsible disclosure.

Contributing

Quick contribution checklist

Before submitting a PR:
  • Code follows SDK patterns
  • Lint passes: make lint
  • Tests pass: make test
  • README documents required permissions
  • No credentials in code or logs

Contribution flow

  1. Fork repository
  2. Create feature branch
  3. Make changes
  4. Run local validation (build, lint, test)
  5. Submit pull request
  6. Address review feedback
  7. Merge
See Publishing for the complete contribution workflow.

Code of conduct

The Baton ecosystem follows the Contributor Covenant Code of Conduct.

Our pledge

We pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.

Standards

Positive behaviors:
  • Demonstrating empathy and kindness
  • Being respectful of differing opinions
  • Giving and gracefully accepting constructive feedback
  • Accepting responsibility for mistakes and learning from them
  • Focusing on what is best for the community
Unacceptable behaviors:
  • Sexualized language or imagery
  • Trolling, insulting, or derogatory comments
  • Public or private harassment
  • Publishing others’ private information without permission
  • Other conduct inappropriate in a professional setting

Enforcement

Report violations to: open-source@conductorone.com All complaints will be reviewed and investigated promptly and fairly.

Governance

Decision making

The Baton ecosystem is maintained by ConductorOne with community input.
Decision typeWho decides
SDK changesConductorOne team
New connectors (ConductorOne org)ConductorOne team
New connectors (your org)You
Feature requestsMaintainers of affected repo

Roadmap

The project roadmap is tracked through GitHub issues in the baton-sdk repository. Community members can:
  • View open issues and planned features
  • Comment on proposed changes
  • Suggest priorities through issue labels

Quick reference

Issue labels

LabelMeaning
bugSomething isn’t working
enhancementNew feature or improvement
documentationDocumentation improvements
good first issueGood for newcomers
help wantedMaintainers want community help