Django DRF Project | Create a New GitHub Respository | 8

[@silvanogonzalez2790]

I appreciate all of your tutorials! I started this series here on KZbin and decided I wanted to support you so I purchased this course on Udemy. I noticed the videos are either different or in different order. Will they both cover the same content or are there some videos on here that are not on Udemy?

[@veryacademy]

At the moment, they are the same videos and should be in the same order, which is worrying. That won't always be the case. There are a few different/more tutorials that won't make it to KZbin, and I use Udemy to help structure the course so I can keep making changes to it. My plan for the course is to squash the first 20 hours into 10 but retain and add value, then move on to the next phase. I am still working on a timeline for that. It is a big job. I have made sure that all the basics are covered to ensure that what is there represents a good start to working with DRF. As you mentioned, it is in many ways that purchasing is about supporting, although you will get access to the source code. I have always made a pledge that learning should be free. At the moment until I can cover the costs of living I will continue to leverage income streams, hopefully, we can move beyond that in the future and host courses for free. Thank you

[@heismyke]

thank you very academy but i have an issue with this course after dragging and droppping my file to the github folder, cant see anything there

[@veryacademy]

Apologies. I would like more info to help you. When you put a file in a folder, you can't see the file?

[@heismyke]

Not that I can’t see the file once I drag and drop the development folder we are working with on the GitHub folder, when I open my GitHub application I just see drf-e-commerce

[@veryacademy]

Hmm, that doesn't really help me understand further, sorry to say. Sorry, this sounds like one of those I need to see to understand. You haven't taken into consideration that I am a little slow and old. @@heismyke

[@heismyke]

Don’t worry. I would try my best to work it out on my own end Thank you very much for this beautiful playlist It is really industry standard

[@veryacademy]

All of this is very much working towards a narrative where I hope to develop a style/course which provides better industrial insights and is closer to an industry dev experience. few things you can check and do: 1. Refresh Repository: In your GitHub application, look for a "Refresh" or "Fetch origin" option. This will update the local copy of the repository with the latest changes from the remote repository on GitHub. 2. Check Branches: Ensure that you are on the correct branch in your GitHub application. If you are working on a specific branch, make sure that branch is selected. 3. Synchronize: Some GitHub applications have a "Synchronize" or "Sync" option. This performs a fetch and pull to update your local repository. 4. Check for Errors: Look for any error messages or notifications in your GitHub application. It might provide insights into what's happening. 5. Command Line Git: Open a command prompt or terminal and navigate to your local repository using the command line. Run the following commands to update your local repository: git fetch origin git pull origin Replace with the name of the branch you are working on. 6. Restart the Application: Sometimes, restarting your GitHub application can resolve display issues. 7. Check .gitignore: Ensure that the files or folders you expect to see are not listed in the .gitignore file, as this file specifies patterns of files that Git should ignore. 8. Check Repository on GitHub: Go to the GitHub website, navigate to your repository, and check if the changes are visible there. This will help you determine whether the issue is with the GitHub application or the repository itself. 9. Re-clone Repository: As a last resort, you can clone the repository again to a new location and see if the issue persists. @@heismyke