Skip to content

copilot-verifier: Include in mainline #622

Closed

Description

@ivanperez-keera

Description

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.

Further notes

None.

Activity

  1. added
    CR:Type:ManagementAdmin only: Change request for conformance with policies or procedures
    CR:Status:InitiatedAdmin only: Change request that has been initiated
    on May 16, 2025
  2. RyanGlScott commented on May 16, 2025

    @RyanGlScott
    Collaborator

    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?
  3. ivanperez-keera commented on May 17, 2025

    @ivanperez-keera
    MemberAuthor

    Change Manager: Confirmed that the issue exists.

  4. added
    CR:Status:ConfirmedAdmin only: Change request that has been acknowledged by the change manager
    and removed
    CR:Status:InitiatedAdmin only: Change request that has been initiated
    on May 17, 2025
  5. ivanperez-keera commented on May 17, 2025

    @ivanperez-keera
    MemberAuthor

    Technical Lead: Confirmed that the issue should be addressed.

  6. added
    CR:Status:AcceptedAdmin only: Change request accepted by technical lead
    and removed
    CR:Status:ConfirmedAdmin only: Change request that has been acknowledged by the change manager
    on May 17, 2025
  7. ivanperez-keera commented on May 17, 2025

    @ivanperez-keera
    MemberAuthor

    Technical Lead: Issue scheduled for fixing in Copilot 4.5.

    Fix assigned to: @RyanGlScott .

  8. added
    CR:Status:ScheduledAdmin only: Change requested scheduled
    and removed
    CR:Status:AcceptedAdmin only: Change request accepted by technical lead
    on May 17, 2025
  9. added this to the 4.5 milestone on May 17, 2025
  10. ivanperez-keera commented on May 17, 2025

    @ivanperez-keera
    MemberAuthor

    @RyanGlScott Just copy it as is, and we can make the changes later (separately).

    Include the example and the Dockerfile where they are and under the copilot-verifier directory.

  11. 1 remaining item

  12. RyanGlScott commented on Jun 20, 2025

    @RyanGlScott
    Collaborator

    Implementor: Solution implemented, review requested.

  13. added
    CR:Status:VerificationAdmin only: Change request that is currently being verified
    and removed
    CR:Status:ScheduledAdmin only: Change requested scheduled
    on Jun 20, 2025
  14. ivanperez-keera commented on Jun 21, 2025

    @ivanperez-keera
    MemberAuthor

    Change Manager: Verified that:

    • Solution is implemented:
      • The code proposed compiles and passes all tests. Details:
        Build log: https://app.travis-ci.com/github/Copilot-Language/copilot/builds/275542308
      • 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.
  15. ivanperez-keera commented on Jun 21, 2025

    @ivanperez-keera
    MemberAuthor

    Change Manager: Implementation ready to be merged.

  16. added
    CR:Status:ClosedAdmin only: Change request that has been completed
    and removed
    CR:Status:VerificationAdmin only: Change request that is currently being verified
    on Jun 21, 2025
  17. added a commit that references this issue on Jun 28, 2025
    894f0aa
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

CR:Status:ClosedAdmin only: Change request that has been completedCR:Type:ManagementAdmin only: Change request for conformance with policies or procedures

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions