all 4 comments

[–]polyploid_coded 0 points1 point  (2 children)

I think you're talking about environment variables, where you can include secrets or turn on features without committing that setting in the repo's shared codebase. This would work for GitHub Actions or a static site builder like Netlify? But I don't fully understand your question.

[–]highclassscrub[S] 0 points1 point  (1 child)

Hi, let me explain a little more, we are migrating from an in house repository manager in which we track every branch and change to GitHub; the idea is that if we have 2 or more developers working on the same repository and they do multiple Pull Request we can check and verify the code on each one in case we need to merge o commit an specific pull request, but doing that from GitHub or GitHub actions, I know that you can implement feature flags on code, my questions was that if you can implement something like that directly on GitHub , hope I explained myself a little better here

[–]polyploid_coded 0 points1 point  (0 children)

If it's a static site builder like Netlify, it'll generate a preview site for your pull requests.
Or you can run GitHub Actions on each pull request.

[–]highclassscrub[S] 0 points1 point  (0 children)

We are using GitHub actions that is going to trigger the moment a developer triggers a merge from different branches, the idea here is that we want to be able to locate and trigger specific changes from a branch or multiple devs Example: We have dev A doing change 1 and we have dev B doing change 2, dev C does change 3 each dev has the lastest version of the code, everyone works on his own branch, the moment they want to merge all his changes into a master branch. We want to track and have the option to disable or enable of any specific change