>I am changing to updating the records on they fly rather than upgrading,
so
>the version number is really not that important. New records use a version
>signature and don't compare to the citserver version so no conflict.
Sounds good. We are officially changed over from ctdlmigrate
Forgot to say that I was not logged in either and that was what was causing
the check-in. I did not notice since I had access to everything.
Strange
I am changing to updating the records on they fly rather than upgrading, so
the version number is really not that important. New records use a version
signature and don't compare to the citserver version so no conflict.
Oh, and I pushed the release button a few times, so when the visit merge is
done we'll have to adjust the version numbers being applied.
> If not then I'll merge and then troubleshoot. I think when we tell it
>not to squash the commits, it brings in your entire commit history
>followed by a merge commit.
Ok, I went ahead and tried it. It did exactly that. The commits that make
up the merge are written to the log an
I had the same problem, and then I realized I was not logged in. Any chance
that's happening to you?
If not then I'll merge and then troubleshoot. I think when we tell it not
to squash the commits, it brings in your entire commit history followed by
a merge commit.
Tried to create a new Merge Request for a different branch and when I click
to create it, the page just spins and never creates it. Something is up
with GitLab
> Thu Jul 20 2023 02:28:36 PM EDT from HarlowSolutions Subject: Re:
>Approval Request: Memory_Leak_SmtpClient
>
>
>
>Either I
Either I do not have permission to merge, or something is wrong with
GitLab. When I bring up the Merge Request, the left menu has a bunch of
spinning updates that never complete. I was able to assign the merge to
myself, but that did not change anything, except there is a warning on my
icon that
Geez. Nice find. Approved, of course.
