Skip to content

Learning CodeQL docs: add COBOL notes and remove links #2487

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Dec 3, 2019

Conversation

jf205
Copy link
Contributor

@jf205 jf205 commented Dec 3, 2019

This PR adds notes (in the form of a snippet) about the future of COBOL support to 'CodeQL for COBOL' in the 'Learning CodeQL' project and in a couple of places in the 'Support' project. The two links to the soon-to-be-removed LGTM URLs have also been deleted.

@felicitymay, do you think these notes appear in the correct places?

I've also bumped the version number for the projects that use global-conf/py and the 'CodeQL training' project.

@jf205 jf205 added this to the 1.23 milestone Dec 3, 2019
@jf205 jf205 requested a review from shati-patel as a code owner December 3, 2019 11:01
Copy link
Contributor

@felicitymay felicitymay left a comment

Choose a reason for hiding this comment

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

Thanks for these updates. Generally they look good.

https://jenkins.internal.semmle.com/job/Docs/job/Generate-Sphinx/1125/artifact/target/sphinx/learn-ql/cobol/introduce-libraries-cobol.html has a link to LGTM help about the query console which should probably be omitted too.

Copy link
Contributor

@felicitymay felicitymay left a comment

Choose a reason for hiding this comment

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

Thanks for the update. All LGTM.

@felicitymay felicitymay merged commit 37e9ff1 into github:master Dec 3, 2019
@jf205
Copy link
Contributor Author

jf205 commented Dec 4, 2019

This was merged into master, but it should have been rc/1.23 (my fault). I'll revert and open a new PR against the correct branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants