DFFML Rolling Alice: Engineering Logs: Volume 1: Coach Alice, 7 Jul 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Coach Alice: Volume 1: Chapter 2: Part: 33: Meta Issue Body As Output Operation

Description

https://github.com/intel/dffml/pull/1401#issuecomment-1170489046

A

A

Let's look at this so.

A

Look at this rickman's community standard contribution right when I got this back here we got named Temple here's the contribution, here's the issue, readme's buddy Okay, so now we'll say: reading contribution.

A

And it takes, you should read me and it's your body.

A

Now, what is this return? Well, it returns a electronic community standard contribution.

A

A

Okay, so this returns a recommended, Community standard contribution.

A

A

A

But that's not part of it, so pretty path.

A

It's a path issue. It looks good, so read my contribution. So now we need another output operation here which will I'll put a list of reading contributions.

A

A

A

Okay, so we're gonna grab from the output operation code and it puts the group that group okay.

A

Attack her best breakfast solve sctx definition.

A

Okay. So what is this thing going to do? Manage your body? Okay? So, what's going to be recommended, Community standards? Okay, so this is.

A

Collect the community standard contributions.

A

Okay, so this should return a list of contributions um because it's going to grab nctx definition.

A

A

I'm quite template by okay, so this is a definition, so we want to pass recommendation standard contribution. Okay, so.

A

Okay, so this grabs all the um this- should grab all of the inputs of that type from the network, and then that way we should be able to add overlays which just create readme. It should be making that message contribution and we could should do that for other files and then you can take the okay readme issue.

A

Read my issues getting run, no matter what she's bad, so it should take readme path.

A

It should take the wrong path. Like I said this should so, let's do this maybe run, if is a need for a readme.

A

ah Man, this is not two.

A

Oh man, okay, this is.

A

Okay, too, okay, so two o'clock, we have 40 minutes. Okay, we have 40 minutes. What is the rest of the things we need to do to make this work?

A

A

Okay, so what do we got here for briefing mm-hmm.

A

Read the issue read my commit message: readme contribution.

A

Okay, that's who we just were and then in pull requests. We have read me PR, which takes an issue.

A

Or request reference issue, purpose body we do PR title.

A

A

A

All right read me: MD.

A

Let's go read my path: let's go bring me back.

A

Okay, so read my path: okay, read my first not exist. Give me contribution.

A

So there's issue, then we put the issue. Otherwise we just put the path.

A

Foreign, okay,.

A

So all we need to do is make this output operation work.

A

A

Make this output operation work and then.

A

Okay, all it is it's reading contribution.

A

Not complicated at all, okay, um just gotta, do it: okay, so collect record contributions.

A

Branch, okay can I show an example of a pull request to the honest branch within the next 35 minutes, which includes updated, contributing documentation on how to.

A

Produce a brief okay! No, no, no I cannot it's not gonna happen. There's no way that that will happen. Okay,.

A

A

A

Not a realistic assumption. Okay.

A

Okay, not a realistic exception, all right out of realized. Okay,.