Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Julian Joseph - Feedback

Open
#212 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github, github-actions, vscode

Research direction

The issue mentions CumulusCI, SalesforceDX, GitHub Actions, VS Code, GitHub Codespaces, and Code Builder, but names no repository files, tests, or entry points. Start by reviewing the reported workflow comparison and related feedback; the issue is not complete until a specific product change and acceptance criteria are defined.

Written by the indexing model from the issue text.

Description

area:General Feedback

What is your role?
Salesforce DevOps Engineer
What do you normally work on when building on the Salesforce Platform?
Managed Packages
What tools do you use today to develop on the Salesforce Platform?
CumulusCI, SalesforceDX, GitHub Actions, VS Code (local), GitHub Codespaces (trying it out)
How do you see Code Builder fitting into your current workflow? Will it replace any tools you are currently using?
I can't really see how it would fit in yet. No really sure if this is meant for my use case, but so far I rather use something like Codespaces rather than Code Builder.
General feedback
Definitely interesting but just having trouble figuring out how it adds or replaces the workflow I've got.

Dominant language
No language data
Stars
35
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from forcedotcom/code-builder-feedback

All issues in forcedotcom/code-builder-feedback

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.