GithubHelp home page GithubHelp logo

dviz-course's People

Contributors

arunavsk avatar ashutosh1919 avatar chalghouma avatar dependabot[bot] avatar devinw-sudo avatar eharguin avatar ephemerant avatar fralfaro avatar johnyrufus avatar jonathanbranam avatar keviv202 avatar larryzhang95 avatar noman0008 avatar nratkiew avatar phui avatar qke avatar rachithaiyappa avatar shusingh avatar vincentmwong avatar yy avatar yzjing avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

dviz-course's Issues

Squashing before merging PR commits

Professor @yy, I noticed while working on some PRs (#51 and #48) that the repository doesn't have squashing enabled yet. Squashing is nothing but combining all the commits of the PR into a single one and merging the PR as a single commit. If this is something that you think is helpful, then you just need to enable the squash merging in the repository setting.

Once this feature is enabled, we don't need to do anything else. From next time onwards, You will see option Squash and Merge on all PRs. Instead of just Merge, you can click on Squash and Merge and it will squash all the commits into single commit.

Advantage of Squash Merge:

  • Experimental commits to test features must not be committed while merging and only the final result of all commits in PR should be merged as a single commit.
  • If PRs have a high number of commits and if we keep merging that, then the .git history size will become very huge in just some months. It will be many times more than the actual repository code itself.

Please close this issue once you see this.

Rendering Notebook diffs

Professor @yy , I have recently raised PR to add one of the feature and noticed that we currently don't have anything which can tell us the diffs in the notebooks changed in case somebody raises a PR. But there is a way in which we can setup a github workflow which will tell the changes in notebook same way git VCS works. We can use ReviewNB for that. Let me know how this idea sound to you. If you think it will be helpful to us, then I will be happy to start working on that.

Automated testing of syntax errors in Notebooks

Professor @yy , Currently we don't have any workflow to test the syntax of the code being contributed to notebooks. I understand that these notebooks are just work assignments and probably may not require thorough testing. But when I ran pytest over all of the notebooks. I found that there are lot of syntax errors (or may be intentional code skip). I am attaching the image of one of such findings.
Screen Shot 2021-08-25 at 8 52 37 AM

More than half of the notebooks are showing some syntax errors in them. Do you think we need automation to test the notebooks whenever the new PR is raised? If yes, then we can start the work on that.

Broken Links and GitHub Workflow

Professor @yy, We have previously seen such a scenario in #34 where we found the broken link while manually reading the material. Instead of relying on manually checking the links after a certain duration, it is good to have a workflow to check links' health status.

As part of the new PR #53, I have added that workflow. After running the workflow, I found out some of links are broken. I have listed all of the broken links with paths below:

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.