Avoiding conflicts in welcome PRs

Problem -
When developers send their welcome PR to the sef-dev repo, it will generate conflicts because the PR’s are sending to update the same JSON file.

Suggested solutions -
@jaye and @Gravewalker suggest Jekyll as a solution for this issue and assign me to work on that.

Progress -
Right now I’m learning how to implement it. And I will update the progress under this thread. Any other suggestions are open from you all. :slightly_smiling_face:

6 Likes

Nice, let me know if you need to take a call or anything

1 Like

Sure I’ll let you know.

1 Like

Thanks for initiating this task, Pasindu. Do your magic! :heart_eyes:

1 Like

Thank you!! @jaye. Will do my best.

2 Likes

Progress update -

For now, did some experiments with Jekyll to create a JSON array with profiles that are created by separate user profiles with MD files.

And it’s locally working now. I post that test repo in Git hub also -
https://github.com/pasindur99/Siri_JekyllTest

@jaye suggests that we will need a separate repo for deploy this Jekyll project. After creating that repo I can create a pull request for test this. :slightly_smiling_face:

2 Likes

This is a good progress @Pasindu_Rupasinghe!! :hugs:

Here’s a preview link of the json output. https://pasindur99.github.io/Siri_JekyllTest/about.json

I tested it for CORS. It won’t be an issue because it returns an Access-Control-Allow-Origin: * header.

curl -vL https://pasindur99.github.io/Siri_JekyllTest/about.json 2>&1 | fgrep -i access-control-allow-origin

returns:
access-control-allow-origin: *

@Gravewalker Could you please create a separate repo for the welcome PRs?
Pasindu, let’s rename the output as profiles.json and remove the unwanted files from the repo.

2 Likes

@jaye I think it’s good to create a new repo instead of using this test one. Because I did a lot of testing in this repository. It’s easy to create a new one without using it.

I can send a PR for that once @Gravewalker creates a repo.

2 Likes

Impressive work @Pasindu_Rupasinghe.

Sure :slightly_smiling_face:

1 Like

@Pasindu_Rupasinghe
Here you go, use this repo https://github.com/sef-global/dev-welcome-pr

2 Likes

Okay. I’ll notify you once my pr has been sent. :slightly_smiling_face:

Thanks @Gravewalker !

PR is ready for this issue.

@jaye @Gravewalker
Please review it and let me know if there is anything that needs to be changed.

1 Like

@Pasindu_Rupasinghe use this url to get the profiles
https://sef-global.github.io/dev-welcome-pr/developers.json

Okay, @Gravewalker I’m working on that.
And I sent a pr to add existing profiles and also to add the pr template.

pr link -

1 Like

Nice work @Pasindu_Rupasinghe lemme create the issues for you. Maybe we might have to break this up to two different PRs??

1 Like

Okay @Gravewalker . I think it would be better.

Merged! Thanks @Pasindu_Rupasinghe !

We need to update the readme guiding them on how to create the welcome PR.

Your welcome @jaye. Thank you for reviewing those prs.

@Gravewalker Would you be able to create issues for,

  1. Update redeme file with guidance in sef-global/ dev-welcome-pr.
  2. Update pull request template in sef-global/ sef-dev.

I think that’s all that I have to do with this task. Please let me know if there are any other tasks that need to be completed.

1 Like

Good job so far, Mr. Siri! You can go ahead and create those issues.
Other things might be, adding the content to the page such as blogs, our repos and stuff.

@Gajindu_Bandara you may switch the IRC task with Pasidu if you like.
I think it might be effective because Pasindu is comfortable with IS related stuffs and you are comfortable with dynamic contents.

1 Like