Skip to content

Commit f8abafe

Browse files
committed
feat: initial release of Memberstack CLI
Full-featured CLI for managing Memberstack apps, members, plans, data tables, records, and custom fields via the GraphQL API. Includes OAuth 2.0 PKCE authentication, JSON/CSV import/export, bulk operations, and a comprehensive Vitest test suite.
0 parents  commit f8abafe

54 files changed

Lines changed: 8555 additions & 0 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.github/CODE_OF_CONDUCT.md

Lines changed: 83 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
# Contributor Covenant 3.0 Code of Conduct
2+
3+
## Our Pledge
4+
5+
We pledge to make our community welcoming, safe, and equitable for all.
6+
7+
We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
8+
9+
## Encouraged Behaviors
10+
11+
While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
12+
13+
With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
14+
15+
1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
16+
2. Engaging **kindly and honestly** with others.
17+
3. Respecting **different viewpoints** and experiences.
18+
4. **Taking responsibility** for our actions and contributions.
19+
5. Gracefully giving and accepting **constructive feedback**.
20+
6. Committing to **repairing harm** when it occurs.
21+
7. Behaving in other ways that promote and sustain the **well-being of our community**.
22+
23+
## Restricted Behaviors
24+
25+
We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
26+
27+
1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
28+
2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
29+
3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
30+
4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
31+
5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
32+
6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
33+
7. Behaving in other ways that **threaten the well-being** of our community.
34+
35+
### Other Restrictions
36+
37+
1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
38+
2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
39+
3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
40+
4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
41+
42+
## Reporting an Issue
43+
44+
Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
45+
46+
When an incident does occur, it is important to report it promptly. To report a possible violation, contact the maintainers via email at hello@flashbrew.digital.
47+
48+
Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
49+
50+
## Addressing and Repairing Harm
51+
52+
If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
53+
54+
1. Warning
55+
1. Event: A violation involving a single incident or series of incidents.
56+
2. Consequence: A private, written warning from the Community Moderators.
57+
3. Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
58+
2. Temporarily Limited Activities
59+
1. Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
60+
2. Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
61+
3. Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
62+
3. Temporary Suspension
63+
1. Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
64+
2. Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
65+
3. Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
66+
4. Permanent Ban
67+
1. Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
68+
2. Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
69+
3. Repair: There is no possible repair in cases of this severity.
70+
71+
This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
72+
73+
## Scope
74+
75+
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
76+
77+
## Attribution
78+
79+
This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
80+
81+
Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
82+
83+
For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).

.github/CONTRIBUTING.md

Lines changed: 116 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,116 @@
1+
# Contributing to Memberstack CLI
2+
3+
Thank you for your interest in contributing! We welcome contributions of all kinds, whether it's reporting bugs, suggesting features, or improving documentation.
4+
5+
By contributing, you agree to abide by our [Code of Conduct](CODE_OF_CONDUCT.md) to ensure a welcoming and respectful community for all.
6+
7+
## Table of Contents
8+
9+
- [Ways to Contribute](#ways-to-contribute)
10+
- [Getting Started](#getting-started)
11+
- [Development Workflow](#development-workflow)
12+
- [Pull Request Process](#pull-request-process)
13+
- [Need Help?](#need-help)
14+
15+
## Ways to Contribute
16+
17+
There are many ways to contribute:
18+
19+
- **Report bugs**: Found something broken? Let us know!
20+
- **Suggest features**: Have an idea for a new command or improvement? We'd love to hear it
21+
- **Improve documentation**: Help make our docs clearer
22+
- **Add features**: Contribute new commands or enhancements
23+
- **Fix issues**: Pick up an issue from our backlog
24+
25+
## Getting Started
26+
27+
### Prerequisites
28+
29+
- Node.js 20+
30+
- pnpm (`npm install -g pnpm`)
31+
32+
### Setup
33+
34+
1. Fork the repository on GitHub
35+
36+
2. Clone your fork locally:
37+
38+
```bash
39+
git clone https://github.com/your-username/memberstack-cli.git
40+
cd memberstack-cli
41+
```
42+
43+
3. Install dependencies:
44+
45+
```bash
46+
pnpm install
47+
```
48+
49+
4. Build the project:
50+
51+
```bash
52+
pnpm build
53+
```
54+
55+
## Development Workflow
56+
57+
1. Create a new branch for your changes:
58+
59+
```bash
60+
git checkout -b feature/your-feature-name
61+
```
62+
63+
2. Make your changes and test thoroughly
64+
65+
3. Run quality checks:
66+
67+
```bash
68+
pnpm type-check # TypeScript validation
69+
pnpm check # Lint check
70+
pnpm test # Run tests
71+
pnpm fix # Auto-fix issues
72+
```
73+
74+
4. Commit your changes with a clear message
75+
76+
5. Push to your fork and create a pull request
77+
78+
## Pull Request Process
79+
80+
### Before Submitting
81+
82+
- Code passes all checks (`pnpm type-check && pnpm check`)
83+
- Tests pass (`pnpm test`)
84+
- Changes build successfully (`pnpm build`)
85+
86+
### PR Guidelines
87+
88+
1. **Clear conventional title**: Describe what changed (e.g., `feat: add plans command`)
89+
2. **Description**: Explain what and why
90+
3. **Link issues**: Reference any related issues (e.g., "Fixes #123")
91+
92+
> Use common sense when drafting your pull request. The goal is to make it easy for maintainers to review and merge your changes. Include sufficient details but at the same time avoid unnecessary information.
93+
94+
### Commit Message Guidelines
95+
96+
This project uses [release-please](https://github.com/googleapis/release-please) to automate changelog and release PRs. Please use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) for all commit messages:
97+
98+
- `feat:` for new features (triggers a new release and changelog entry)
99+
- `fix:` for bug fixes (triggers a new release and changelog entry)
100+
- `chore:`, `docs:`, `refactor:`, etc. for other changes (do not trigger a release)
101+
102+
**Examples:**
103+
104+
- `feat: add plans command`
105+
- `fix: handle missing config error`
106+
- `chore: update dependencies`
107+
108+
Only `feat:` and `fix:` commits will appear in the changelog and trigger a new release. All other commit types are allowed but will not trigger a release.
109+
110+
---
111+
112+
## Need Help?
113+
114+
- **GitHub Issues**: For bug reports and feature requests
115+
116+
Thank you for contributing!

.github/FUNDING.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
github: ["bensabic"]
2+
buy_me_a_coffee: "bensabic"
Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
name: Bug Report
2+
description: Report a bug or unexpected behavior
3+
labels: ["bug"]
4+
body:
5+
- type: markdown
6+
attributes:
7+
value: |
8+
Thanks for taking the time to report a bug!
9+
10+
- type: textarea
11+
id: description
12+
attributes:
13+
label: Description
14+
description: A clear description of the bug
15+
placeholder: What happened?
16+
validations:
17+
required: true
18+
19+
- type: textarea
20+
id: reproduction
21+
attributes:
22+
label: Steps to Reproduce
23+
description: How can we reproduce this issue?
24+
placeholder: |
25+
1. Run 'memberstack ...'
26+
2. See error
27+
validations:
28+
required: true
29+
30+
- type: textarea
31+
id: expected
32+
attributes:
33+
label: Expected Behavior
34+
description: What did you expect to happen?
35+
validations:
36+
required: true
37+
38+
- type: textarea
39+
id: environment
40+
attributes:
41+
label: Environment
42+
description: Please provide relevant environment details
43+
placeholder: |
44+
- Node.js: 20.x
45+
- OS: macOS 14
46+
- Package manager: pnpm 10.x
47+
validations:
48+
required: false
49+
50+
- type: textarea
51+
id: additional
52+
attributes:
53+
label: Additional Context
54+
description: Any other context, screenshots, or error logs
55+
validations:
56+
required: false

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
blank_issues_enabled: false
Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
name: Documentation
2+
description: Report a documentation issue or suggest an improvement
3+
labels: ["documentation"]
4+
body:
5+
- type: markdown
6+
attributes:
7+
value: |
8+
Thanks for helping improve the documentation!
9+
10+
- type: textarea
11+
id: description
12+
attributes:
13+
label: Description
14+
description: What's wrong or missing in the documentation?
15+
placeholder: Describe the issue or improvement
16+
validations:
17+
required: true
18+
19+
- type: input
20+
id: location
21+
attributes:
22+
label: Location
23+
description: Where in the documentation is the issue?
24+
placeholder: e.g., README, CONTRIBUTING, command help text
25+
validations:
26+
required: false
27+
28+
- type: textarea
29+
id: suggested-change
30+
attributes:
31+
label: Suggested Change
32+
description: How would you improve it?
33+
validations:
34+
required: false
Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
name: Feature Request
2+
description: Suggest a new feature or improvement
3+
labels: ["enhancement"]
4+
body:
5+
- type: markdown
6+
attributes:
7+
value: |
8+
Thanks for suggesting a feature!
9+
10+
- type: textarea
11+
id: description
12+
attributes:
13+
label: Description
14+
description: A clear description of the feature you'd like
15+
placeholder: What would you like to see added?
16+
validations:
17+
required: true
18+
19+
- type: textarea
20+
id: problem
21+
attributes:
22+
label: Problem
23+
description: What problem does this solve?
24+
placeholder: I'm always frustrated when...
25+
validations:
26+
required: false
27+
28+
- type: textarea
29+
id: alternatives
30+
attributes:
31+
label: Alternatives Considered
32+
description: Any alternative solutions or workarounds you've considered
33+
validations:
34+
required: false
35+
36+
- type: textarea
37+
id: additional
38+
attributes:
39+
label: Additional Context
40+
description: Any other context, mockups, or examples
41+
validations:
42+
required: false
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
name: Question
2+
description: Ask a question about usage or configuration
3+
labels: ["question"]
4+
body:
5+
- type: markdown
6+
attributes:
7+
value: |
8+
Before asking, please check the markdown files (e.g. README, ARCHITECTURE, etc.) and existing issues for answers.
9+
10+
- type: textarea
11+
id: question
12+
attributes:
13+
label: Question
14+
description: What would you like to know?
15+
placeholder: Describe your question
16+
validations:
17+
required: true
18+
19+
- type: textarea
20+
id: context
21+
attributes:
22+
label: Context
23+
description: Any relevant context about what you're trying to do
24+
placeholder: e.g., command you ran, expected outcome, environment details
25+
validations:
26+
required: false

.github/SUPPORT.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
# Support
2+
3+
Thank you for using the Memberstack CLI! If you need help, please review the following options:
4+
5+
## Documentation
6+
7+
- See the [README](../README.md) for setup and usage instructions.
8+
- Review the [CONTRIBUTING](CONTRIBUTING.md) guide for development and PR tips.
9+
10+
## Bug Reports
11+
12+
- Please open an issue on GitHub with clear steps to reproduce, expected vs. actual behavior, and any relevant logs or screenshots.
13+
14+
## Feature Requests
15+
16+
- Open a GitHub issue labeled as a feature request. Describe your use case and why it would be helpful.
17+
18+
## Self-Service
19+
20+
- Check closed issues and discussions for similar questions or solutions.
21+
- Visit the [Memberstack documentation](https://docs.memberstack.com) for general Memberstack platform help. Issues not related to this CLI tool may be closed without notice.
22+
23+
---
24+
25+
Thank you for helping make this project better! If you have feedback on the support process, please open an issue.

0 commit comments

Comments
 (0)