sindresorhus / gh-latest-repos

Microservice to get the latest public GitHub repos from a user

gh-latest-repos

Microservice to get the latest public GitHub repos from a user

I currently use this on my website.

It returns the latest repos along with some metadata. The result is cached for a day.

Example response

Usage

With now

$ git clone https://github.com/sindresorhus/gh-latest-repos.git
$ now gh-latest-repos --env GITHUB_TOKEN=xxx --env GITHUB_USERNAME=xxx --env ACCESS_ALLOW_ORIGIN=xxx --env MAX_REPOS=xxx

Manual

To deploy on your own hosting provider, check out 11e01ac, set the below environment variables, and start it with npm start.

Environment variables

Define the following environment variables:

• GITHUB_TOKEN - Personal access token.
• GITHUB_USERNAME - The username you like to get repos from.
• ACCESS_ALLOW_ORIGIN - The URL of your website or * if you want to allow any origin (not recommended), for the Access-Control-Allow-Origin header.
• MAX_REPOS - The number of repos returned. Optional. Defaults to 6.

gh-latest-repos's Issues

Make the number of repos returned configurable with an environment variable

Default it to 6 if not specified.

Github Actions & To Say 🙏

Hi @sindresorhus

I found this repo very useful. but i am not that used to working with micro services.

so decided to convert this as a github actions https://github.com/varunsridharan/action-gh-latest-repo/

Thanks for creating a cool project :-)

Add stargazers and fork count for each repo

Description

I like to see the number of stars and forks for my repositories, just like what's seen in Github Profile picture.

Use case is to simulate these cards in other websites.

Properly handling 'just unfrozed' requests

In some cases gh-latest-repos returns just an empty request [].

My hypothesis of cause

I observe in now that a frozen microservice means the process just been killed and only be activated again if a request are made, which is a problem because variables are lost and request to GitHub API have to be reinitiated again.

Because variables are lost, there's race condition between client request and request to GitHub API, hence gh-latest-repos just returns [] instead of waiting for response from GitHub API.

And because of #9 I realized that I can't make a workaround by requesting to gh-latest-repos twice. 😢

Solution

I have my own patch to send 202 (Accepted) without cache control in case empty [] will send (so the client can make another request again)

if (responseText === '[]') {
	response.statusCode = 202;
	response.end('[]');
	return;
}

I can made a PR for this but I realize this is too much for just solving this problem so I have a better idea:

Make fetchRepos() to be synchronous?

Filter out repos without description

Those are usually issue test-cases or other uninteresting stuff.

Would be nice to be able to do this in the GraphQL query, but I have no idea how to achieve that. Alternatively, we could do a fetch, filter, and then if less than MAX_REPOS do another fetch.

---

IssueHunt Summary

[
<
i
m
g

s
r
c

'
h
t
t
p
s
:
/
/
a
v
a
t
a
r
s
0
.
g
i
t
h
u
b
u
s
e
r
c
o
n
t
e
n
t
.
c
o
m
/
u
/
1
1
3
9
2
6
9
5
?
v

4
'

a
l
t

'
y
a
o
d
i
n
g
y
d
'

w
i
d
t
h

2
4

h
e
i
g
h
t

2
4

y
a
o
d
i
n
g
y
d
]
(
h
t
t
p
s
:
/
/
i
s
s
u
e
h
u
n
t
.
i
o
/
u
/
y
a
o
d
i
n
g
y
d
)

h
a
s

b
e
e
n

r
e
w
a
r
d
e
d
.

Backers (Total: $40.00)

• issuehunt ($40.00)

Submitted pull Requests

• #14 Implementation of Filter out repos without description

---

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

---

IssueHunt has been backed by the following sponsors. Become a sponsor