Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BA-1196: add contributing and code of conduct #59

Merged
merged 2 commits into from
Oct 4, 2023

Conversation

deboracosilveira
Copy link
Collaborator

Add contributing and code of conduct

@changeset-bot
Copy link

changeset-bot bot commented Oct 2, 2023

⚠️ No Changeset found

Latest commit: cb257b8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Collaborator

@anicioalexandre anicioalexandre left a comment

Choose a reason for hiding this comment

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

I like it!

CONTRIBUTING.md Outdated

1. Check the [GitHub Issues](https://github.com/silverlogic/baseapp-frontend/issues) to ensure that the feature hasn't already been requested.

2. If the feature hasn't been requested, create a new issue by clicking on the "New Issue" button.
Copy link
Collaborator

Choose a reason for hiding this comment

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

let's make sure people use the right label too, maybe for features requests we could use the enhancement label

CONTRIBUTING.md Outdated
3. Create a new branch for your feature or bug fix:

```
git checkout -b feature-name
Copy link
Collaborator

Choose a reason for hiding this comment

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

if it's not tied to any jira ID we could use BA-feature-name

CONTRIBUTING.md Outdated
5. Commit your changes with a clear and concise commit message:

```
git commit -m "Add feature: Your feature description"
Copy link
Collaborator

Choose a reason for hiding this comment

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

same here, if not tied to any id we could use "BA: feature description"


7. Open a Pull Request (PR) against the `master` branch of the BaseApp repository.

8. Provide a descriptive PR title and include details about the changes you've made.
Copy link
Collaborator

Choose a reason for hiding this comment

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

maybe we could add another step to make sure people read the versioning section on the readme

CONTRIBUTING.md Outdated

1. Check the [GitHub Issues](https://github.com/silverlogic/baseapp-frontend/issues) to ensure that the bug hasn't already been reported.

2. If the issue hasn't been reported, create a new issue by clicking on the "New Issue" button.
Copy link
Collaborator

Choose a reason for hiding this comment

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

let's make sure people use the right label too, maybe for bugs requests we could use the bug label

@deboracosilveira deboracosilveira merged commit 0faff3f into master Oct 4, 2023
5 checks passed
@deboracosilveira deboracosilveira deleted the BA-1196-contributing-guidelines branch October 4, 2023 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants