Fix/splaytree delete last node

.github/workflows/nodejs.yml

@@ -12,8 +12,8 @@ jobs:
     - uses: actions/checkout@master
     - name: Create GH Pages
       run: |
-        git remote set-url origin https://RodrigoDLPontes:${{ secrets.GITHUB_TOKEN }}@github.com/RodrigoDLPontes/visualization-tool.git
-        git config --global user.email "rodrigo.dl.pontes@gmail.com"
-        git config --global user.name "RodrigoDLPontes"
+        git remote set-url origin https://csvistool.com:${{ secrets.VISTOOL_GITHUB_TOKEN }}@github.com/csvistool/visualization-tool.git
+        git config --global user.email "csvistool@gmail.com"
+        git config --global user.name "csvistool"
         npm ci
         npm run deploy

.gitignore

@@ -28,3 +28,4 @@ contrib.txt
 
 # ide settings
 .vscode/
+.history

.vscode/settings.json

@@ -40,5 +40,11 @@
 	},
 	"editor.codeActionsOnSave": {
 		"source.fixAll.eslint": "explicit"
+	},
+	"github.copilot.enable": {
+		"*": false,
+		"plaintext": false,
+		"markdown": false,
+		"scminput": false
 	}
 }

CONTRIBUTING.md

@@ -6,21 +6,21 @@ Hi there! This document outlines some rules for contributing to the site.
 
 There is a lot that still needs to be improved, ranging from implementing more data structures and algorithms, making slight modifications to existing ones, bug fixing, updating the UI and making general improvements. Whatever your interest in web development is, you can probably improve your skills by contributing in that regard!
 
-For more details on what needs to be done, check out the [Issues tab](https://github.com/RodrigoDLPontes/visualization-tool/issues).
+For more details on what needs to be done, check out the [Issues tab](https://github.com/csvistool/visualization-tool/issues).
 
 ## Structure
 
 The site was created using [create-react-app](https://github.com/facebook/create-react-app) application. It also uses [Single Page Apps for GitHub Pages](https://github.com/rafrex/spa-github-pages) for compatibility with GitHub Pages.
 
-[`src/algo/`](https://github.com/RodrigoDLPontes/visualization-tool/tree/master/src/algo) contains data structure/algorithm-specific scripts
+[`src/algo/`](https://github.com/csvistool/visualization-tool/tree/master/src/algo) contains data structure/algorithm-specific scripts
 
-[`src/anim/`](https://github.com/RodrigoDLPontes/visualization-tool/tree/master/src/anim) contains the base animation API
+[`src/anim/`](https://github.com/csvistool/visualization-tool/tree/master/src/anim) contains the base animation API
 
-[`src/screens/`](https://github.com/RodrigoDLPontes/visualization-tool/tree/master/src/screens) contains the top-level screens (the homepage, the algorithm screen)
+[`src/screens/`](https://github.com/csvistool/visualization-tool/tree/master/src/screens) contains the top-level screens (the homepage, the algorithm screen)
 
 ## Animation API
 
-The animation API is very well documented [here](https://www.cs.usfca.edu/~galles/visualization/source.html). However, some changes have been made to it as part of the conversion to ES6, so existing JavaScript files are also a good reference for learning how to do things. All functions can be found in [`AnimationMain.js`](https://github.com/RodrigoDLPontes/visualization-tool/blob/master/src/anim/AnimationMain.js).
+The animation API is very well documented [here](https://www.cs.usfca.edu/~galles/visualization/source.html). However, some changes have been made to it as part of the conversion to ES6, so existing JavaScript files are also a good reference for learning how to do things. All functions can be found in [`AnimationMain.js`](https://github.com/csvistool/visualization-tool/blob/master/src/anim/AnimationMain.js).
 
 ## Dev Environment Setup
 
@@ -52,7 +52,7 @@ To make a PR:
 
 1. Create a new pull request
 2. Click “Compare across forks”
-3. Base repo should be RodrigoDLPontes/master and head repo should be the relevant branch on your fork
+3. Base repo should be csvistool/master and head repo should be the relevant branch on your fork
 4. Name the PR something simple and descriptive
 5. In the description, make sure to reference the issue you worked on (such as “closes #155”, “addresses #150”, etc)
 6. Add anything else to the description that you think makes your changes more understandable