ersilia
ersilia copied to clipboard
Test and workflows to check readme file changes on master
Fixes #177
I am looking into the error but what I feel is since the superior branch is named 'master', the issue arises as it works for a superior branch named 'main'
Hi @sayantani11 this is great stuff. Do you think we should rename master to main? (master is old nomenclature in github as you may know). I am afraid of doing so at this stage because many people are currently contributing to ersilia and this may cause problems. What are your thoughts?
Hi @sayantani11 this is great stuff. Do you think we should rename master to main? (master is old nomenclature in github as you may know). I am afraid of doing so at this stage because many people are currently contributing to ersilia and this may cause problems. What are your thoughts?
Yes, it can create a chaos for the people who are new to git as well. So what I feel is we can hold this for now!! And after 20th we can focus on renaming the branch for this.... As it will be just two more days of the contribution period. What say?
Completely agree with you. Let's keep this on hold
@miquelduranfrigola Can you rename the branch?
Hi @sayantani11,
We are making some changes to the repository structure, including creating a Docker image for it, so we will rename the branch when we release all these new features. Then we will merge the PR as well. Sorry this cannot be merged at this moment but many thanks for the work you have done, it will get merged hopefully next week!
@GemmaTuron this pull request is very interesting. Can we please try to merge it, or at least learn the relevant GitHub Actions contributed?
@GemmaTuron any progress here?
@GemmaTuron I am trying to resolve this issue but I am running into conflicts at the moment. Can you please check?
Hey, since @sayantani11 is participating in this round, this might be a good moment to close the issue. @miquelduranfrigola and @sayantani11 I get an error on the Setup of the pull request that says "Error: The log was not found. It may have been deleted based on retention settings."
@GemmaTuron @miquelduranfrigola I can actually look into this issue again! And try to figure what's the problem maybe
Sorry, I overlooked this PR - my apologies. @sayantani11 is doing amazing work on other fronts. So, @sayantani11 - if you have time to work on it, great. If not, I would deprioritise this PR for now.