You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The copilot-verifier was developed outside of this repo, but there's interest in having all Copilot projects and libraries merged into a main repo for ease of management.
Type
Management: files need to be moved between repos.
Additional context
None.
Requester
Ivan Perez.
Method to check presence of bug
Not applicable (not a bug).
Expected result
The last state of the copilot-verifier is included in this repository, disregarding history, and adjusting the changelog to make the old
issues refer to copilot-verifier#<ISSUE_NUM> so that they are not interpreted as related to the main Copilot repo.
Desired result
The last state of the copilot-verifier is included in this repository, disregarding history, and adjusting the changelog to make the old
issues refer to copilot-verifier#<ISSUE_NUM> so that they are not interpreted as related to the main Copilot repo.
Proposed solution
Copy last state of copilot-verifier as subdirectory of main repo.
Adjust Changelog in copilot-verifier to make older issues point to correct repo.
I briefly looked into this, and I have some questions about how to handle certain aspects of the copilot-verifier repo:
Should I list myself as the maintainer in copilot-verifier.cabal, or should I list you (as is done for other copilot subpackages)?
Do we still want to include the Dockerfile from the copilot-verifier repo?
There are a variety of examples under the copilot-verifier/examples subdirectory. Should I try to move these examples to copilot/examples (where the bulk of the Copilot examples are currently stored), or should I keep this examples within the copilot-verifier subdirectory?
The solution proposed produces the expected result. Details:
The following dockerfile checks out the latest version of copilot-verifier, v4.4, and compares it against the version being merged, ignoring differences in the CHANGELOG (which is expected to be different), checking that there are no other differences, after which it prints the message "Success":
FROM ubuntu:noble
ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get update
RUN apt-get install --yes git
RUN git config --global advice.detachedHead false
CMD git clone $REPO $NAME \
&& cd $NAME \
&& git checkout $COMMIT \
&& cd .. \
&& git clone -b v4.4 https://github.com/Copilot-Language/copilot-verifier copilot-verifier-original \
&& diff --exclude 'CHANGELOG' -r $NAME/copilot-verifier copilot-verifier-original/copilot-verifier \
&& echo "Success"
Command (substitute variables based on new path after merge):
$ docker run -e REPO=https://github.com/GaloisInc/copilot-1 -e NAME=copilot -e COMMIT=9e0dcac323f523277b1bdcb74869d823b6ad5324 copilot-verify-622
Implementation is documented. Details:
CHANGELOG updated to make old issues point to original repo. No other changes needed.
Change history is clear.
Commit messages are clear.
Changelogs are updated.
Examples are updated. Details:
No updates needed.
Required version bumps are evaluated. Details:
Bump not needed; change includes existing package without affecting API.
Activity
RyanGlScott commentedon May 16, 2025
I briefly looked into this, and I have some questions about how to handle certain aspects of the
copilot-verifierrepo:copilot-verifier.cabal, or should I list you (as is done for othercopilotsubpackages)?Dockerfilefrom thecopilot-verifierrepo?copilot-verifier/examplessubdirectory. Should I try to move these examples tocopilot/examples(where the bulk of the Copilot examples are currently stored), or should I keep this examples within thecopilot-verifiersubdirectory?ivanperez-keera commentedon May 17, 2025
Change Manager: Confirmed that the issue exists.
ivanperez-keera commentedon May 17, 2025
Technical Lead: Confirmed that the issue should be addressed.
ivanperez-keera commentedon May 17, 2025
Technical Lead: Issue scheduled for fixing in Copilot 4.5.
Fix assigned to: @RyanGlScott .
ivanperez-keera commentedon May 17, 2025
@RyanGlScott Just copy it as is, and we can make the changes later (separately).
Include the example and the
Dockerfilewhere they are and under thecopilot-verifierdirectory.1 remaining item
copilot-verifier: Adjust issue numbers in changelog. Refs Copilot-Lan…
copilot-verifier: Document changes in CHANGELOG. Refs Copilot-Languag…
Explicitly list .cabal files in cabal.project. Refs Copilot-Language#622
copilot-verifier: Include in mainline copilot repo. Refs Copilot-Lang…
copilot-verifier: Adjust issue numbers in changelog. Refs Copilot-Lan…
copilot-verifier: Document changes in CHANGELOG. Refs Copilot-Languag…
RyanGlScott commentedon Jun 20, 2025
Implementor: Solution implemented, review requested.
ivanperez-keera commentedon Jun 21, 2025
Change Manager: Verified that:
Build log: https://app.travis-ci.com/github/Copilot-Language/copilot/builds/275542308
The following dockerfile checks out the latest version of
copilot-verifier, v4.4, and compares it against the version being merged, ignoring differences in the CHANGELOG (which is expected to be different), checking that there are no other differences, after which it prints the message "Success":CHANGELOG updated to make old issues point to original repo. No other changes needed.
No updates needed.
Bump not needed; change includes existing package without affecting API.
ivanperez-keera commentedon Jun 21, 2025
Change Manager: Implementation ready to be merged.
Merge branch 'develop-copilot-verifier-upstream'. Close Copilot-Langu…