secret env vars and (generic) file storage files: control whether it's available in pull request builds
from guido marucci blas on 2016/02/03 15:08:20 +0000 currently secret env variables are not available for any pr no matter if it is an internal pr or a pr from a forked repo. i would be nice to have grained control over this and allow secret en variables to be visible for pr from the same repo. co…
we’re glad to announce that this feature is now available in production on [bitrise.io](http://bitrise.io) :tada:

related [#changelog](/c/6-changelog) / [#announcements](http://discuss.bitrise.io/tags/announcements) :

[image]

[secret env vars and (generic) file storage files: control whether it’s available in pull request builds](http://discuss.bitrise.io/t/secret-env-vars-and-generic-file-storage-files-control-whether-it-s-available-in-pull-request-builds/2790) [changelog](/c/changelog)

related [#feature-r…](/c/9-feature-request)
[image] paulaniculaesei:

but if i make from vs code a new branch , why i can’t open a pull request?

because you need to push the branch to somewhere public first. you can’t push your branch to someone else’s repository, so you need your own (a fork in github terms). [image] dueck456:

is there an easy way to detect when new code is flashed to the device so i can reinitialize the retained variables?

below is a link to a post by [@rickkas7](/u/rickkas7) about storing retained data in a struct.

[image] dueck456:

saving a know value to eeprom jumps to mind

there is … hello and welcome [@jhmauritz](/u/jhmauritz).

yes, changing the variables should be enough to connect to the server, and using docker-compose is absolutely a viable option.

if the server is publicly available you should configure ssl as well, otherwise your connections to it won’t be secure.

mind that although y… its kind difficult to understand in my POV but not impossible  

imagining it while reading


can you show some codes? or samples on what you want to achive? ```
#!/usr/bin/perl
use strict; 
use warnings; 

my $gia = '12tai';

#Capture sequence of digits into one variable,
#capture sequence of non-digits into another variable
my ($number, $name) = $gia =~ m/(\d+)(\D+)/;

print "$number $name\n";#Two values separated by one space
``` The Hidden Power type isn't copied. If you Transform into something with Hidden Power, the Hidden Power will be the same type as Ditto's IVs.


[Here](https://www.smogon.com/forums/threads/hidden-power-iv-combinations.78083/)'s a list of Hidden Power IV Combinations if you need it. tab visibility is currently only based on the user profile sheet. if you want to control tab visibility from a value in another sheet, you need to use relation/lookup, relation/rollup, or single value columns to bring in whatever value you need into the user profile sheet.

[https://docs.glideapps.c…](https://docs.glideapps.com/all/reference/design-and-structure/visibility-conditions#tab-visibility) i’m afraid not at this time but it’d make for a great [feature request](https://community.devkinsta.com/c/feature-requests/6)! this feature is currently not available for this product.  it has been added to the features request list and is being looked at by engineering and if possible may be added at a later date. interesting.... hmm, it looks that the ./bin/elasticsearch script is requiring the keystore password input from stdin

if you look at the actual script that starts ./bin/elasticsearch you can see why.

from the script

# get keystore password before setting java options to avoid

# conflicting gc con…