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

Changes not appearing on website https://awesome-go.com/ #3815

Closed
TheArchDev opened this issue Oct 8, 2021 · 5 comments · Fixed by #3940
Closed

Changes not appearing on website https://awesome-go.com/ #3815

TheArchDev opened this issue Oct 8, 2021 · 5 comments · Fixed by #3940

Comments

@TheArchDev
Copy link
Contributor

I've noticed that some recent changes (eg #3805 #3807 #3808 ) merged a couple of days ago have yet to propagate to the public website hosted at https://awesome-go.com/ . What's the process (manual or automated) for such code changes in the repo appearing on that website too? Maybe the process could be captured in the CONTRIBUTING.md file for contributors to understand?
Thank you!

@kitarp29
Copy link

@TheArchDev I have some past experience in Web Developement.
I think I can help with this issue.
Please assign it to me.

@earthboundkid
Copy link
Contributor

It looks like this is still a problem. Are the devs aware of this? @avelino?

avelino added a commit that referenced this issue Dec 15, 2021
fixed: #3815

Signed-off-by: Avelino <avelinorun@gmail.com>
@avelino
Copy link
Owner

avelino commented Dec 16, 2021

for some reason travisci stopped working, I created an issue to migrate to github actions #3943

avelino added a commit that referenced this issue Dec 16, 2021
fixed: #3815

Signed-off-by: Avelino <avelinorun@gmail.com>
@earthboundkid
Copy link
Contributor

Thanks!

@avelino
Copy link
Owner

avelino commented Dec 16, 2021

Thanks!

@carlmjohnson Thank you for creating the issue notifying of the problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants