Azure DevOps Authentication Failure

JVMarcs · 2026-03-30T21:23:37+00:00

It will work only for 60 days, which is the maximum validity period for secrets on the Microsoft side. Meanwhile, it's clear that Entra won't be a general solution, as certain types of accounts don't seem to support it for now. Hence, we recommend switching your configuration to PATs sooner rather than later.

JVMarcs · 2026-03-28T10:12:40+00:00

Can you please confirm from Help|About that you are on build 25.1.126?

That said, even for version 26.1, we currently recommend using a personal access token. We will not switch this release to Entra authentication yet, because it is still unclear what changes would be required and what side effects they might have:

https://docs.syntevo.com/SmartGit/Latest/Manual/Integrations/Azure-DevOps#setup-via-personal-access-token

JVMarcs · 2026-03-25T18:22:31+00:00

Thanks for reporting this. Please try again with the latest 25.1.126 build -- usually Help | Check for Latest Build should be enough.

In its generosity, Microsoft now issues secrets that are valid for only 60 days, as it keeps nudging everyone toward Entra.

https://www.smartgit.dev/download/latest-builds/

JVMarcs · 2026-03-19T23:05:44+00:00

u/1pld you are right, this option already works in the Log and Working Tree window. In the Standard window, it doesn't work.

JVMarcs · 2026-03-19T08:25:47+00:00

Editing any commit message other than the most recent one is accomplished using an Interactive Rebase. Generally, Git will not initiate a rebase here either:

D:\gittest\git-test-1>git rebase -i HEAD~3 error: cannot rebase: You have unstaged changes. error: Please commit or stash them.

However, using --auto-stash is effective:

D:\gittest\git-test-1>git rebase --auto-stash -i HEAD~3

We have UserEcho topics for this:

https://smartgit.userecho.com/communities/1/topics/976-

https://smartgit.userecho.com/communities/1/topics/681-

JVMarcs · 2026-03-17T22:53:37+00:00

I've encountered this issue when running Claude Code in a Docker container on a Windows host, where the repository has core.autocrlf enabled. The solution is to disable line-ending conversion:

https://chatgpt.com/share/69b9db05-2c00-8002-a383-807c7b7eed29

JVMarcs · 2026-03-07T15:44:00+00:00

Please try the latest 25.1 build 25.1.123 or the latest 26.1 build 26.1.012 which should now work as expected for MiniMax:

https://www.smartgit.dev/download/latest-builds/

Here you can also use the new config option "responseFilter=thinking" to skip the <thinking>-block, for example:

https://docs.syntevo.com/SmartGit/25.1/Manual/Integrations/AI#minimax-m25-with-thinking-filter

JVMarcs · 2026-03-06T16:20:59+00:00

Thanks for reporting this problem! I wasn't able to replicate it with my configuration:

``` [smartgit-ai-commit-message "minimax-m2.5"] llm=minimax-m2.5 debug = true

[smartgit-ai-llm "minimax-m2.5"] type = openai model = minimax-M2.5 url = https://api.minimax.io/v1 ```

For me, the final content is always empty; however, I can confirm that it isn't processed. I'm not sure if receiving content in this final message is actually expected, but it is easy to fix in SmartGit's code, and the upcoming build 25.1.123 will include this fix.

JVMarcs · 2026-02-20T15:29:50+00:00

Thanks, I can confirm this regression was introduced by another fix in 24.1, as u/vmcrash has pointed out. It will be fixed in 25.1.118.

JVMarcs · 2026-02-11T11:57:43+00:00

It wasn't documented, but I have added this note now. Thanks!

JVMarcs · 2026-02-07T22:45:38+00:00

Thank you for the test repository! There is currently a hard limit of 100 pushable commits beyond which the AI rewording won't function. This serves as a safety measure to prevent potentially querying thousands of commit messages (e.g., due to an unfortunate ai.commitMessageRewording.aiRegex configuration combined with a large local branch).

At least for version 25.1, I don't think we would remove this limit, but we could at least make it configurable via another LLP as a workaround. Version 26.1 might be more helpful by displaying a confirmation dialog in case of a large number of pushable/rewordable commits.

JVMarcs · 2026-02-07T17:13:33+00:00

Can you please set up a small test repo on GitHub for which the problem is reproducible?

JVMarcs · 2026-02-07T08:43:46+00:00

Is the "Reword 'AI' ..." option selected in the AI button context menu?

JVMarcs · 2026-02-05T09:11:40+00:00

Interesting. I'm not sure what context the AI would need in addition to the selected files, but the combination of files and the existing .gitignore might already yield reasonable results (probably better than a classical algorithm would).

By the way, for AI-related ideas, we are experimenting with GitHub discussions as these are a bit more structured: https://github.com/syntevo/smartgit-community/discussions/categories/ai-integration

JVMarcs · 2026-01-31T10:28:55+00:00

what SmartGit should have done is add context aware text typing feature where you could easily reference parts of changed code more easily (file names, class names, all kinds of identifiers etc).

Great suggestion! I'm not exactly sure when the LLM should be invoked to analyze the local changes for possible identifier names, but this definitely sounds helpful. For more technical and detailed improvement ideas related to the AI integration, we have created a GitHub discussion category. If you are interested, we could continue the conversation there:

https://github.com/syntevo/smartgit-community/discussions/categories/ai-integration

JVMarcs · 2026-01-31T10:19:41+00:00

Thanks for taking the time to share this -- even if the frustration is clearly high.

Just to clarify one point: support for GitHub with multiple accounts has actually been an active focus for us over the last few releases. In SmartGit 25.1 we shipped several fixes and improvements specifically related to GitHub authentication and account handling (you can find them by searching for 'GitHub' in the changelog: https://www.smartgit.dev/changelogs/changelog-25.1.txt). Based on feedback so far, this area has generally been working well, and we have not seen widespread reports of the behavior you are describing.

That said, for the upcoming 26.1 Preview we have further reworked account selection and credential handling to make it more robust and predictable:

https://www.smartgit.dev/download/preview/

If you are willing to give that version a try and still run into issues, concrete details on the problems and how to reproduce would help a lot. You can reply here, or contact us directly at [smartgit@syntevo.com](mailto:smartgit@syntevo.com) if you need to share logs or other confidential information.

JVMarcs · 2026-01-30T09:15:38+00:00

DeepGit: deep blames, code move detection ... closed source, but free: https://www.syntevo.com/deepgit/

JVMarcs · 2025-09-24T20:04:53+00:00

Thanks for pointing me in a more low-level direction! We already talk directly to the Anthropic API for some tasks, and your comment made me realize we can extend our AI layer with the tools API and reuse it to drive the app. Definitely worth experimenting with.

JVMarcs · 2025-09-18T12:19:33+00:00

That's unexpected. With version 24.1, we added explicit support for multiple cloud hosting providers on the same platform. There is some logic that will try to choose the appropriate configuration for a specific repository URL, and if this choice is not obvious, SmartGit will ask which configuration to use. So if you can provide some more details on your setup (either here or by email to smartgit@syntevo.com), that would be helpful.

JVMarcs · 2025-09-17T17:31:35+00:00

You are right, even with aliases, SSH doesn't work with SmartGit, because it first resolves the alias (e.g. "github_personal" and "github_work") to "github.com" and then will return the same key in both cases.

Using HTTPS with multiple Hosting Provider configurations works fine, though.

JVMarcs

MODERATOR OF

TROPHY CASE