Skip to content

Conversation

@cmungall
Copy link
Member

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR enables Copilot by adding a dedicated setup workflow and streamlining the Copilot instructions.

  • Introduces .github/workflows/copilot-setup-steps.yml to install ROBOT, OBO scripts, Python tools, and configure the environment for Copilot.
  • Replaces the detailed .github/copilot-instructions.md with a single-line symlink to ../CLAUDE.md.
  • Adds a robot-version input but continues to hard-code version references in cache keys and download URLs.

Reviewed Changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File Description
.github/workflows/copilot-setup-steps.yml New CI job to set up required tools (ROBOT, obo-scripts, uv, Python)
.github/copilot-instructions.md Replaced full instruction content with a symlink to external file
Comments suppressed due to low confidence (2)

.github/workflows/copilot-setup-steps.yml:45

  • The robot-version input is not used here; the cache key—and similarly the download URLs—are hard-coded to v1.9.7. Parameterize these values using ${{ inputs.robot-version }} to respect the input.
        key: ${{ runner.os }}-robot-v1.9.7

.github/copilot-instructions.md:1

  • This file now only contains a symlink reference and all previous Mondo ontology guidelines were removed. Ensure those guidelines remain accessible—either by migrating them or updating references—so developers aren’t left without critical documentation.
../CLAUDE.md

@cmungall cmungall requested a review from twhetzel July 11, 2025 01:48
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see this is symlinked to CLAUDE.md, however a lot of what was in this file is not in the CLAUDE.md file and these examples look useful. Should more content from the copilot instructions file be moved into the CLAUDE.md file?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I definitely encourage trying adding more examples!


- name: Add obo-scripts to PATH
run: |
git clone https://github.com/cmungall/obo-scripts.git ${{ github.workspace }}/tools/obo-scripts
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do the obo-scripts exist in any other project directory vs. a personal repo? for initial testing these seems ok

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure I follow the Q....

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is cloning a repo in your personal GitHub space, which is ok for now. I was asking if this repo with obo-scripts existed anywhere else within an existing project.

run: |
mkdir -p ~/.jar-cache
if [ ! -f ~/.jar-cache/robot.jar ]; then
curl -L https://github.com/ontodev/robot/releases/download/v1.9.7/robot.jar -o ~/.jar-cache/robot.jar
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ODK version 1.5.4 uses ROBOT version 1.9.8. is something incompatible with this ROBOT version?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or to ask it another way - why not just use ODK instead of downloading the JAR file?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you can figure out how to do that!

ai4curation/aidocs#5

@caufieldjh
Copy link
Member

Would it be enough to include this under copilot-setup-steps?

container: obolibrary/odkfull:latest

jobs:
# The job MUST be called `copilot-setup-steps` or it will not be picked up by Copilot.
copilot-setup-steps:
runs-on: ubuntu-latest
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
runs-on: ubuntu-latest
runs-on: ubuntu-latest
container: obolibrary/odkfull:1.6

Lets just try this?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@caufieldjh
Copy link
Member

I think the instructions will need to include an introduction to the ODK toolset and some examples.
In a perfect world without the need for trial and error, this would mean including the entire OBOOK text.
I don't think we're quite at that point yet, but there is also the chance that the underlying model may have some ODK exposure already.
Only one way to find out.

@cmungall cmungall merged commit 9d4fc30 into master Jul 25, 2025
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Set up github copilot for this repo

5 participants