This is a meta-issue. When voting, please include your favorite platform (or just upvote other comments for that platform). Also, comment if this process must work locally (which may not be possible with the current LLM technology today).

JetBrains IDE's Git tool is capable of using an AI Assistant to generate commit messages powered by Artificial Intelligence. All changed files are listed and I can select the files to include in the commit message to be generated, as staged changes. After confirming, the AI Assistant analyzes the changes and automatically generates the commit message. This is a useful time saver and boring task killer that I would love to have available in SmartGit features.

Ref.: https://blog.jetbrains.com/idea/2023/06/ai-assistant-in-jetbrains-ides/

Below are some examples of commit messages generated through artificial intelligence:

Refactor handling of config file and enhance port validation regex

This commit updates the handling of a configuration file in the 'circuitid.py' script.
Previously, the file was only opened for writing but now it's also being opened for reading directly after it's written to. This is done to ensure that the configurations are properly loaded.

Furthermore, the regular expression used for port validation was updated. The previous pattern did not limit then length of the port and accepted any string that started with letters followed by numbers. Now, the port requires being 2 to 16 alphanumeric characters long, which helps standardize the port labeling system.

Refactor circuit ID generator for better readability and performance

Updated the circuit ID generator Python script to improve code readability and performance. Major changes include breaking down functionalities into smaller, more manageable functions and translating comments from Portuguese to English to make them accessible to a wider audience. Additionally, the procedural code was refactored to an object-oriented model wherein functions were encapsulated within a class, CircuitIDGenerator. Variable names were also updated for clarity. These changes help improve maintainability of the code and provide a clearer structure for understanding the logic behind circuit ID generation. The script also now checks if it is run as the main program before creating an instance of the CircuitIDGenerator class to start the application.

It should be possible to configure gitea as a hosting provider. 

This would allow to work with pull requests and code reviews. 

WSLg can be used to run SmartGit in Linux environment while using Windows as main development OS.

We have tried it briefly and SmartGit seems to mostly work file in WSLg.

Out findings are summarized here:

https://docs.syntevo.com/SmartGit/HowTos/Running-on-WSLg.html

There are a few nuisances, such as SmartGit updates failing, which can be improved.

The current plan is to spend a couple days in the next couple months to try to fix nuisances.

However, if this proves to be complicated, we'll get back to more popular feature requests, unless this topic gains more votes.

If you're interested in using WSLg with SmartGit, please describe your use cases and any problems you encountered.

Note: this topic is about running SmartGit from within WSLg. If you want to access repositories on WSL from Windows, vote for topic 1409.

In the Git-Flow 'Finish Feature' dialog is should be possible to select ‘Create Pull Request..’ as well. 

Hi,

I use a lot GIT Rerere. It's really powerful when you have to deal with lots of conflicts (this depends on your GIT usage of course).

One of the most complicated point with this tool (in my opinion) is that you have very little visibility on available recorded resolutions.

That's why I think it would be very helpful in a GIT GUI like Smartgit to be able to see a list of recorded resolutions. Or maybe to highlight the fact that a conflict was auto-solved by GIT Rerere when it is the case.

An other hard part with GIT Rerere is to deal with wrong conflict resolutions. Once you recorded a wrong conflict resolution, it is hard to know how to revert this using the forget command.

I think a GUI tool showing where Rerere did its magic and allowing to undo this magic and forget the matching resolution would be just the perfect tool to make Rerere easy to use.

I'm sure there's other great things to do about GIT Rerere in a GUI, but there's so many interesting subjects....

I hope you'll have the opportunity to add this to Smartgit one day :) 

Thanks again for your great work

We have hundreds of branches in our project. They are created automatically for every issue and bug. When I need to find and clone specific branch, it is really hard to find them in the long list. There is search, but that is not very useful, because it only jumps to the first matching branch name. It would be really helpful to be able to filter the branches, to type part of the name and the view would only display matching branches.

GitLab uses git "push options" to allow CI to be skipped for a specific push. We push the same commit to multiple branches and use the git push option when we don't want CI to be run. Putting a CI skip in our commit message would not work because we want CI to run for some of our pushes, and because with our use cases, CI skip would not make sense to have stay in our commit history.

The ability to check a box when I am doing a push to specify that I want to skip CI for that push would be awesome.

I don't care about any other git push options right now, but it might be worth considering that people might come up with new & useful ways to use git push options over time.

Similar to Sourcetree, in the commit dialog I'd like to see which branch I'm committing and pushing to, to avoid committing to the wrong branch.

Please add an icon/modifier (similar to the green and red arrows) to a repo in the repository view if you are in a local branch that you have not pushed.  We often end up in a situation where a developer has created a release or feature branch but did not push it.  There is not obvious/quick way to spot local branches like you can spot uncommitted changes (red icons) or unpushed commits (red arrow).

Regularly, I fetch, pull, and push multiple repos via the multi-select repo feature.  SG sequentially executes the command for each repo.  Would it reduce the elapsed time for all by having SG execute them concurrently (or in batches, such as 5 repos at a time)?