-
Notifications
You must be signed in to change notification settings - Fork 228
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
Publicar Contagem e mineração de dados de investigação com Unix #2532
Publicar Contagem e mineração de dados de investigação com Unix #2532
Conversation
Publicar contagem-mineracao-dados-investigacao-unix
Inclusão do DOI
Dear @anisa-hawes the build is failing because of a broken link in this lesson: Found 635 internal links in the cache...
HTML-Proofer found 1 failure! I found a video that I think is similar to the one referenced on that link: https://www.youtube.com/watch?v=7sEMKXrRaAs |
Hello @DanielAlvesLABDH. Funnily, I've actually updated that link before! In PR #2461 I found a couple of possible alternative links to the interview. This one https://devchat.cachefly.net/rubyrogues/RR215SonicPi.mp3?rss=true provides full audio of the podcast episode that is referenced. I have a few minutes now, so I can update /en/lessons/sonification with this new link, and @JimmyMedeiros82 can update #429! |
Update broken link to the interview with Sam Aaron, para.382 of en/lessons/sonification.
Great! Thanks a lot! |
Update done in programminghistorian/ph-submissions#429 @anisa-hawes and @DanielAlvesLABDH |
Revisão final
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@DanielAlvesLABDH está pronta a publicar :)
Publicar tradução da lição Counting and mining research data with Unix
Checklist
Closes #ISSUENUMBER
to the description aboveIf you are having difficulty fixing build errors, first consult https://github.com/programminghistorian/jekyll/wiki/Making-Technical-Contributions carefully, especially "Common Build Errors". Then contact the technical team if you need further help.