Skip to content

Commit 523c700

Browse files
Update README.md
1 parent 06ce8d8 commit 523c700

File tree

1 file changed

+29
-37
lines changed

1 file changed

+29
-37
lines changed

README.md

Lines changed: 29 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -63,43 +63,35 @@ participate in the community and showcase your full range
6363
of abilities. This is why we have this *unofficial* ranking.
6464

6565
## Commits
66-
Make sure that you turn on
67-
private commits in the API, as was
68-
instructed above, so that you can simply
69-
create a diary, for example. It will generate
70-
a lot of commits.
71-
72-
Another option is to simply create a tutorial website,
73-
even if it is not tech-related. Don't you know
74-
that the markdown is really for blogging back then?
75-
(Don't get me wrong, blogging is still relevant today.)
76-
It simplifies everything, even a tutorial website.
77-
Markdown is the default markup language of GitHub,
78-
particularly for the README file.
79-
80-
Or, if you are a writer writing stories, do that in
81-
GitHub. Others were already using GitHub for
82-
laws articles, to-do lists, music compositions,
83-
itineraries etc.
84-
85-
You can check
86-
[this](https://github.com/xdvrx1/github-pages-tutorial)
87-
out if you are not familiar
88-
with GitHub Pages.
89-
90-
## Contributed To
91-
The `Contributed To` component as part of the
92-
computation is when you create pull requests
93-
and are merged to the `main` branch.
94-
95-
It's not always about submitting
96-
proposed changes in a code base,
97-
even simply changing something at the
98-
README file of others will do. What I did was
99-
a pull request to add a Page View on a README file.
100-
If you click the README file of others, then click
101-
the edit button, it will automatically create a fork.
102-
Then, edit the file and create a pull request.
66+
If you did create your own instance of the app
67+
[like this](https://github.com/anuraghazra/github-readme-stats?tab=readme-ov-file#deploy-on-your-own),
68+
make sure you turn on private commits
69+
in the API `include_all_commits=true`.
70+
If you are privately coding, professionally or personally,
71+
that will be counted.
72+
73+
Another option is to create a tutorial website, tech or non-tech.
74+
Markdown, originally designed for
75+
blogging, simplifies creating content. It is the default
76+
markup language for GitHub, especially for README files.
77+
78+
If you are a writer, consider writing your stories on
79+
GitHub. Many people use GitHub for various purposes, such
80+
as legal articles, to-do lists, music compositions, and
81+
itineraries.
82+
83+
Additionally, you can generate commits by:
84+
85+
- Contributing to documentation for open-source projects.
86+
- Participating in discussions and issue tracking.
87+
- Creating and maintaining wikis.
88+
- Managing project boards and tasks.
89+
- Uploading design assets or artwork.
90+
- Sharing research notes or academic papers.
91+
92+
For more information on creating websites with GitHub,
93+
check out
94+
[this tutorial](https://github.com/xdvrx1/github-pages-tutorial) about GitHub Pages.
10395

10496
## Your Stars
10597
Take note, this is not the stars on GitHub when you

0 commit comments

Comments
 (0)