Skip to content
This repository has been archived by the owner on Apr 29, 2024. It is now read-only.

feat: Add new chapter on practical application #35

Merged
merged 36 commits into from
Apr 3, 2024
Merged
Changes from 1 commit
Commits
Show all changes
36 commits
Select commit Hold shift + click to select a range
811e420
Add new chapter
BekahHW Jan 19, 2024
667a27a
Add a starter idea
BekahHW Jan 22, 2024
7ff0c9a
Add issue templates
BekahHW Jan 22, 2024
c553f4f
Update title
BekahHW Jan 22, 2024
efc6cbc
Add section on writing first issue
BekahHW Jan 22, 2024
e288853
Add images
BekahHW Jan 22, 2024
89d29bb
Updates
BekahHW Feb 19, 2024
967000f
Clean up
BekahHW Feb 19, 2024
4b599f2
Fix merge conflicts
BekahHW Feb 19, 2024
d1d1290
fix: punctuations and adjust wording
adiati98 Feb 21, 2024
dea57c9
Merge branch 'main' into feat/get-practical
BekahHW Mar 11, 2024
2e2b83f
Fix coc formatting
BekahHW Mar 11, 2024
7b9b38b
Remove unused asset
BekahHW Mar 11, 2024
c8e554d
Make the bug report section clearer
BekahHW Mar 11, 2024
ec49e5f
Fix up template sections
BekahHW Mar 11, 2024
3b9da89
fix: format and a broken link
adiati98 Mar 11, 2024
693e9c1
fix: unordered list format
adiati98 Mar 11, 2024
f33c3a6
Add a template for contributing guide
BekahHW Mar 14, 2024
4e797e5
Fix typo
BekahHW Mar 14, 2024
79dd86a
Add more detail to feature section
BekahHW Mar 14, 2024
f6103e6
Use code block to make directions clearer
BekahHW Mar 14, 2024
d7f0903
Fix formatting
BekahHW Mar 14, 2024
372908d
Replace insight page with workspace
BekahHW Mar 14, 2024
4951e75
Merge changes
BekahHW Mar 14, 2024
e0e3988
Remove code block formatting
BekahHW Mar 25, 2024
45f607d
Add Readme template
BekahHW Mar 25, 2024
7fbab50
Add a section about license
BekahHW Mar 25, 2024
08ab48b
Fix headings
BekahHW Mar 25, 2024
88bd262
fix: capitalize README
adiati98 Mar 25, 2024
ca5aae3
fix: wording and punctuations for clarity
adiati98 Mar 25, 2024
fb5ebe7
fix: indentation and add syntax highlight
adiati98 Mar 25, 2024
d4875ba
Standardize headings
BekahHW Mar 28, 2024
b104d95
Add checkboxes
BekahHW Mar 28, 2024
7852ee4
Remove Chapter numbers and add getting practical
BekahHW Mar 28, 2024
aec10f3
fix: small wording fixes
adiati98 Mar 28, 2024
380ae66
fix: update titles on README to follow the title of each chapter inst…
adiati98 Mar 28, 2024
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Add section on writing first issue
  • Loading branch information
BekahHW committed Jan 22, 2024
commit efc6cbc0fec924b21c5cb971a4cbb123f0ae9999
20 changes: 15 additions & 5 deletions getting-practical.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,10 @@ Now that you have the repository, you can either edit it directly in GitHub or c


## Set Up Contributing Guidelines
- Create a new file named `CONTRIBUTING.md` in your repository.

Your project will likely have similar contribution guidelines to other projects. You can use the following steps to create your own guidelines, and we'll share the OpenSauced Contributing Guidelines below as an example. Feel free to use those guidelines and update as you see fit for your project.

- Create a new file named `CONTRIBUTING.md` in the root of your repository.
- Outline the process for submitting issues and pull requests.
- Include coding standards, style guides, or any specific requirements.
- Mention how contributors can ask for help or clarification.
Expand Down Expand Up @@ -200,10 +203,17 @@ body:
required: false
```

Write your first issue
- In your repository, click on "Settings" and then "Issues."
- Set up issue templates for bug reports, feature requests, etc.
- Add labels to your repository like "good first issue," "enhancement," "bug," etc.
### Writing Your First Issue

- In your repository, click on the "Issues" tab and then the "New issue" button
![create issue](./assets/images/create-issue.png)
- Select the type of issue you want to create. In this example, we'll select Feature Request.
- Write your issue. If you're following along the example, we'll write a feature request for a new resource.
- Once you've completed the issues, click "Submit new issue."

In this example, we'll write a feature request for a new resource for #100DaysOfOSS.

![feature-form.png](./assets/images/feature-form.png)



Expand Down