Skip to content

docs: rewrite README, add CONTRIBUTING with conventional commits#100

Merged
sudiptob2 merged 2 commits intoarmadaproject:masterfrom
sudiptob2:docs/rewrite-basic-docs
Feb 15, 2026
Merged

docs: rewrite README, add CONTRIBUTING with conventional commits#100
sudiptob2 merged 2 commits intoarmadaproject:masterfrom
sudiptob2:docs/rewrite-basic-docs

Conversation

@sudiptob2
Copy link
Collaborator

What

Rewrite README for clarity and add a CONTRIBUTING guide with conventional commit conventions.

Why

The README had stale version numbers (Spark 3.5.3 / Scala 2.13.15 instead of 3.5.5 / 2.13.8), an incorrect E2E script name, a wrong set-version.sh
argument format, and an outdated client-mode config example. Contributing guidelines and commit conventions were not documented anywhere, making it
hard for new contributors to follow project standards.

Changes

  • Rewrote README: fix default versions to match pom.xml, add CI version matrix table, add architecture overview, remove stale "local://" client-mode
    prefix, fix script names and argument formats, point development section to CONTRIBUTING.md
  • Add CONTRIBUTING.md covering development setup, conventional commits, PR process, coding standards, and Claude Code usage
  • Update /commit slash command to enforce conventional commit format with types, scopes, and examples
  • Fix CLAUDE.md: correct set-version.sh argument format and remove Spark 4.1 from CI matrix description (not in build.yaml)

Signed-off-by: Sudipto Baral <sudiptobaral.me@gmail.com>
@sudiptob2 sudiptob2 marked this pull request as ready for review February 13, 2026 17:07
Signed-off-by: Sudipto Baral <sudiptobaral.me@gmail.com>
@@ -0,0 +1,28 @@
Create a GitHub issue markdown file from the details provided by the user.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any reason not to use the "gh" command to create the actual issue in https://github.com/G-Research/spark/issues rather than just a markdown file?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I considered that as well. However, since we create issues across different boards/projects, sometimes in armada-spark and sometimes in gr/spark, I kept it simple for now and generated a markdown file instead.

- `### Steps to Reproduce` — numbered list (if applicable)
- `### Expected Behavior` — 1-2 sentences
- `### Actual Behavior` — include relevant log snippets in code blocks, keep them short (trim stack traces to the key lines)
- `### Potential Root Cause` — based on your codebase investigation, explain where the issue likely lives. Link to source code using upstream GitHub URLs: `https://github.com/armadaproject/armada-spark/blob/master/...#L<start>-L<end>`. For Apache Spark references, link to the `apache/spark` repo at the relevant tag.
Copy link
Collaborator

@GeorgeJahad GeorgeJahad Feb 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the master branch changes a lot. A "sha" based url like this:

https://github.com/sudiptob2/armada-spark/blob/c92e9e868a9f35fd14fd201d0b783a11c7e7dae5/.claude/settings.json#L8-L11

would be more stable/accurate.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried, but Claude occasionally generates the wrong SHA, causing broken links. It needs some investigation, but should be doable.

Copy link
Collaborator

@GeorgeJahad GeorgeJahad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, left a couple of minor notes. thanks @sudiptob2 !

@sudiptob2 sudiptob2 merged commit 62b35c9 into armadaproject:master Feb 15, 2026
12 checks passed
@sudiptob2 sudiptob2 deleted the docs/rewrite-basic-docs branch February 15, 2026 16:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants