The PR on GitHub should have a step-by-step guide on how to test the change so work through this. Start testing and report any issues on GitHub In this example the login screen will show the changes that were made in that PR. Now when you login to your ClassicPress-dev site you should have those PR files included. You may get another warning message but stick with the default to leave any changes on develop, and select ‘Switch branch’. You can select any one of these from the list, such as Revise login page link layout (PR #795). ![]() Then click on the ‘Current branch’ tab and switch over to see the ‘Pull requests’. To start testing PRs you only need to go into GitHub Desktop and first make sure that the current repository is set as the version you have in XAMPP. Add a PR to your localhost version of ClassicPress It is a good idea to create a site for testing that you are familiar with, so you can see if anything looks different or doesn’t work properly. You can start installing plugins and a theme, and upload items to the media library. To login to your new site, use the address localhost/classicpress-dev/src/wp-login.php. Of course, you will need the database name, username and password that you entered when you created the database. You should be able to complete the setup of ClassicPress in the usual way. Go to your browser and visit localhost/classicpress-dev/src. Note that the actual ClassicPress installation files are in the src folder. 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. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |