If you now go to the classicpress-dev folder in XAMPP you should see a lot of files have been added.
You might be shown one more message, but leave it as the default, hit ‘Continue’ and wait while the clone downloads. Hit the ‘Clone’ button when you are ready. Select your own fork of ClassicPress from the dropdown list, and make sure the local path is entered to the correct XAMPP directory, in this case C:\xampp\htdocs\classicpress-dev\. Open GitHub Desktop and select ‘Clone repository’ from the ‘File’ menu. Now we add in the files for ClassicPress. Once the database is created, go into the XAMPP directory and add a folder for the files in this example we will create a folder called classicpress-dev in the htdocs folder.
Your setup screen will look something like this… XAMPP uses phpMyAdmin so the simplest method is to make a user and select the options to also create a database with the same name, and apply the necessary permissions. You will first need to set up a database, but make sure it creates either a MySQL or MariaDB type. There are plenty of online tutorials about using XAMPP (or any of the other web server stack packages) so this won’t be covered in much detail. This tutorial will take you through the required steps. An easy way to do this is to set up a local version of ClassicPress using a program such as XAMPP on your computer and link it to GitHub Desktop. Once you are comfortable with this concept, the next stage in contributing is to start testing and reviewing other PRs that have been submitted.
#Github desktop login how to#
You can enable experimental symlink support within Windows by installing the Link Shell Extension (it is strongly recommended to read through that entire page to be aware of its shortcomings and Windows' general disdain towards symlinks) and adding the following to your C:\Users\\.In previous GitHub Desktop tutorials we showed you how to submit a pull request (PR), so you could start contributing to the development of an open-source project such as ClassicPress. Then also tell `git` to not automatically convert LF to CRLF by adding the following to your C:\Users\\.gitconfig file:
#Github desktop login install#
Install a good text-editing software such as Notepad++ to work around this make sure to set the correct line terminators in Settings → Preferences… → New Document → Format (Line ending) to “Unix (LF)”: Windows' built-in text editing software doesn't support the line terminators used in Linux text files. By default, Git will do its best to transparently convert file attributes to and from Windows-acceptable formats to the ones on the remote repository, but edits are not always possible (such as with two symlinked files).
NTFS, the default filesystem for Windows, does not support many features that the more modern filesystems Linux supports such as symlinks, file attributes (including the extremely important executable bit), etc. Windows users should take some extra precautions when editing Linux-spawned files.
0 kommentar(er)
