-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Running task on all subrepositories #41
Comments
The idea is to implement a gulp task called e.g.
Usage (with param):
Contents of 'use strict';
/**
* {String} packagePath
* {Minimatch} params
*/
module.exports = ( packagePath, params ) => {
}; |
First use case that we have for this task is #149. But there are obvious other ones like bumping year, dependencies in package.json, updating JSCS rules, etc. |
I've just thought that we could make |
What has been determined so far:
|
In #36 we are discussing how to run some common task on all subrepositories. For example, we need to change the years in the copyright header. We could run a task directly from the
ckeditor5
repo on each of its subrepositories, but this means that this task would need to know everything about its subrepositories (e.g. which files are ignored). This knowledge of course is discoverable, but it would make more sense if subrepositories were running the task themselves.The idea that we have is that subrepositories will have a grunt task (or some other API) which will accept a path to a file with a task source and name of that task. This way the main repo will be able to run one of its tasks in all subrepos. The task's code will be kept in the main repo, but the task will be run directly in subrepos, so the logic on which files it should be run will be local.
The text was updated successfully, but these errors were encountered: