Version Control in V11

Hi Alan,

In PHPRunner version 11, the ability to roll back to previous versions of your project is intended to help manage changes made during the development process, especially in a multi-developer environment. Here's how you can manage version control and rollbacks in PHPRunner:

Rolling Back Changes in PHPRunner V11

1. Version History: PHPRunner keeps a history of project versions. To access this feature:

   • Open your PHPRunner project.
   • Go to the "Project" menu.
   • Look for an option like "Version History" or "Project History." Here, you can view previous versions of your project and restore them if necessary.
   
   
   
   

2. Rollback: If your other developer makes changes that need to be reverted:

   • Navigate to the version history.
   • Select the version you want to roll back to and confirm the rollback.
   
   
   
   

Setting Up a Git Repository

If you find that the built-in versioning in PHPRunner doesn't meet your needs, using Git for version control is a great alternative. Here’s a brief guide to help you set up Git with PHPRunner:

1. Install Git: Make sure Git is installed on your machine. You can download it from git-scm.com.

   
   

2. Initialize a Git Repository:

   • Open your terminal or command prompt.
   • Navigate to your PHPRunner project directory.
   • Run the command git init to create a new Git repository.
   
   
   
   

3. Add Your Project Files:

   • Use git add . to stage all your project files for the first commit.
   • Commit your changes with git commit -m "Initial commit".
   
   
   
   

4. Create a .gitignore File: This file should include patterns for files and directories that you want to exclude from version control (e.g., compiled files, cache, etc.).

   
   

5. Collaborating with Other Developers:

   • Share the repository with your other developer.
   • Encourage them to create separate branches for their changes. This way, they can make changes without affecting the main branch until they are ready to merge.
   
   
   
   

6. Merging Changes: When your developer finishes their changes:

   • They can create a pull request (if using a platform like GitHub or GitLab) or you can review their changes and merge them into the main branch.
   
   
   
   

7. Rolling Back Changes: If a mistake occurs:

   • You can revert changes using commands like git checkout <commit_id> to go back to a specific commit or git revert <commit_id> to create a new commit that undoes the changes.
   
   
   
   

Resources

• For more detailed instructions on Git, you can refer to the official Git documentation.
• There are many tutorials and guides available online, such as GitHub's Learning Lab which provides interactive learning experiences.

Using Git alongside PHPRunner can significantly enhance your project's version control and collaboration, allowing you to efficiently manage changes and rollbacks.

If you have any more specific questions or need further assistance, feel free to ask!

Best,
[Your Name]

I don't appear to have a Version History or Revision History when I open the Project menu unless I'm looking the wrong place.

I don't think this has been added into V11 yet, I've not seen this in the single dev version. In this blog post, V11.1 looks to have version control with GIT mid June so hopefully it's not long away.
https://xlinesoft.com/newsletter/linux_version_and_v111_news

I know the revisions are in v10.91 in the events, this is where it in in v10.91.

This opens this menu on the right.

Thanks

I probably missed that because I wasn't using V11 at the time thought it would be a while before I would be switching to it. That changed when my client decided they could make some small changes like menus, and label changes, so I had him buy a license. Not sure about that decision now.

Hopefully V11.1 is close to being released. I am not sure how well Git would work but will just have to see how easy it is to see what changes what changes were made to specific pages and how easy to rollback.

I don't know if the Project Export would have everything needed or not. I don't think Save As would be a reasonble solution.

I think I might be having to make more database backups during the day so I could restore the Dev database back to an earlier version or have the client hold off on making any changes until V11.1 is released and I see if it will work.

My main error was looking at the V11 announcement from 2023 and assuming that the rollback feature would be available when V11 was released.

How are people handling this now?