{"action":"opened","issue":{"url":"https://api.github.com/repos/nextflow-io/nextflow/issues/840","repository_url":"https://api.github.com/repos/nextflow-io/nextflow","labels_url":"https://api.github.com/repos/nextflow-io/nextflow/issues/840/labels{/name}","comments_url":"https://api.github.com/repos/nextflow-io/nextflow/issues/840/comments","events_url":"https://api.github.com/repos/nextflow-io/nextflow/issues/840/events","html_url":"https://github.com/nextflow-io/nextflow/issues/840","id":351183181,"node_id":"MDU6SXNzdWUzNTExODMxODE=","number":840,"title":"Allow access to manifest scope during workflow execution","user":{"login":"ewels","id":465550,"node_id":"MDQ6VXNlcjQ2NTU1MA==","avatar_url":"https://avatars3.githubusercontent.com/u/465550?v=4","gravatar_id":"","url":"https://api.github.com/users/ewels","html_url":"https://github.com/ewels","followers_url":"https://api.github.com/users/ewels/followers","following_url":"https://api.github.com/users/ewels/following{/other_user}","gists_url":"https://api.github.com/users/ewels/gists{/gist_id}","starred_url":"https://api.github.com/users/ewels/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ewels/subscriptions","organizations_url":"https://api.github.com/users/ewels/orgs","repos_url":"https://api.github.com/users/ewels/repos","events_url":"https://api.github.com/users/ewels/events{/privacy}","received_events_url":"https://api.github.com/users/ewels/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-08-16T12:26:16Z","updated_at":"2018-08-16T12:26:16Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Over at @nf-core we're trying to establish nice config best practices. With the inclusion of the new `manifest.nextflowVersion` variable, it's making increasing sense to bundle all variables describing the workflow into the `manifest` scope as follows:\r\n\r\n```nextflow\r\nmanifest {\r\n  name = 'nf-core/rnaseq'\r\n  description = 'Nextflow RNA-Seq analysis pipeline, part of the nf-core community.'\r\n  homePage = 'https://github.com/nf-core/rnaseq'\r\n  author = 'Phil Ewels, Rickard Hammarén'\r\n  pipelineVersion = '1.0dev'\r\n  mainScript = 'main.nf'\r\n  nextflowVersion = '>=0.31.1'\r\n}\r\n```\r\n\r\nThis is readable and tidy, and works as expected when checking the pipeline config with `nextflow config`. However, it's not possible to access these manifest variables from _within_ the workflow script (`main.nf`). Attempting to do so triggers the following error:\r\n```\r\nERROR ~ No such variable: manifest\r\n```\r\n\r\nIs it possible to make these accessible from within the pipeline script in the same way as other variables? We have discussed this once before (see #597) and I know that we could just use `params.everything` instead, but it doesn't feel as tidy 🤓 "}}
{"actor":{"display_login":"ewels"}}